You know, if you have Windows 2000 or higher in your organization, you could
just go IPSec, and secure all transmissions, not just SQL.
You have two options on the server in the Server Network Utility in the SQL
Program group, you can A) enable the possibility of encryption by installing
multi-protocol and enabling encryption in the properties or B) Set up SSL,
then check force encryption on the general tab.
--
*******************************************************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andy_mcdba@yahoo.com
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
Andy_mcdba@yahoo.com gets filled up to the account
limit with spam every couple of hours now so replies may
not be possible. I will remove this disclaimer once every
ISP involved with relaying the spam can help me out.
*******************************************************************
[quoted text, click to view] "Mariusz" <groovejazz@hotmail.com> wrote in message
news:080701c38295$4f47f640$3101280a@phx.gbl...
> Hi,
>
> I would like to know whether the data transfered between
> ODBC client and SQL Server (eg.2000) is protected.
> Is there any encryption at the SQL transmission level or
> it is transfered in "clear text".
>
> As I know, strong encryption may be forced but it
> requires fyrther setup on SQL server.
>
> I will appreciate info on that, thanx.
>
> Regards,
> Mariusz