Secure Replication in 2000/2005

Hi all:

I have a few questions concerning SQL Server over SSL. I am running SQL
Server 2000 SP3 on ServerA and have enabled Force Protocol Encryption using
a self-signed certificate and everything appears to be working great. I
have verified the encryption is working by using an Ethereal network sniff.

My question is this:

1. Will this now encrypt the SQL sent from any application...meaning the
applications do not need to be modified to take advantage of this?

2. If I am using transactional replication to replicate data to another SQL
Server 2000 SP3 machine (ServerB), will this traffic be encrypted as well or
do I need to do anything extra here?

Any help or resource links would be greatly beneficial.

Thanks in advance!


.

Relevant Pages

  • Re: SSIS as part of scheduled job fails
    ... might not have Encryption support, but it shouldn't be trying to use SQL ... Microsoft SQL Server Management Studio ...
    (microsoft.public.sqlserver.dts)
  • Re: SSL Sicherheitsfehler
    ... SQL Server 2005 german evaluation enterprise installiert ... Die Encryption war die ganze Zeit aus.Dann kam der SSL Fehler. ... SQL Server herstellen. ... TURN ON SSL encryption on the SQL ...
    (microsoft.public.de.sqlserver)
  • Re: Data encryption for results of query using ADO
    ... i read somewhere that there is a way to encrypt and xml output from sql ... > I'm using ADO to connect to a SQL Server. ... > Can I enable encryption for a specific connection to the SQL Server without ...
    (microsoft.public.sqlserver.programming)
  • Re: Utility
    ... I think you are referring to the ability to encrypt source code. ... the encryption method isn't very ... There are third party tools that claim to help secure your SQL Server ...
    (microsoft.public.sqlserver.server)
  • Force Protocol Encryption - Please help!
    ... I just recently set up a SQL 2000 server and have a question about ... so I enabled the Force Protocol Encryption ... After installing the cert, I was once again able to start my SQL ...
    (microsoft.public.sqlserver.security)