Connect to SQL Server dialog box

I am studying the MCP book, and in Ch 10 (regarding SQL
authorization) it says:
The user name and password are submitted to SQL Server
2000 in clear text unless both the client and the server
Net-Libraries are using SSL encryption for the
entire session.

>--Original Message--
>Does anyone know if the SQL Server connection dialog box
transmit the password in clear text? I know it's hidden
from display but I'm wondering what it does behind the
scenes.
>Thanks,
>Ray Kurpiel
>.
>
Thanks for the response, Meryl.

Connect to SQL Server dialog box

I am studying the MCP book, and in Ch 10 (regarding SQL
authorization) it says:
The user name and password are submitted to SQL Server
2000 in clear text unless both the client and the server
Net-Libraries are using SSL encryption for the
entire session.

>--Original Message--
>Does anyone know if the SQL Server connection dialog box
transmit the password in clear text? I know it's hidden
from display but I'm wondering what it does behind the
scenes.
>Thanks,
>Ray Kurpiel
>.
>Thanks for the response, Meryl.

Connect to SQL Server dialog box

Does anyone know if the SQL Server connection dialog box transmit the password in clear text? I know it's hidden from display but I'm wondering what it does behind the scenes
Thanks
Ray KurpielI am studying the MCP book, and in Ch 10 (regarding SQL
authorization) it says:
The user name and password are submitted to SQL Server
2000 in clear text unless both the client and the server
Net-Libraries are using SSL encryption for the
entire session.
>--Original Message--
>Does anyone know if the SQL Server connection dialog box
transmit the password in clear text? I know it's hidden
from display but I'm wondering what it does behind the
scenes.
>Thanks,
>Ray Kurpiel
>.
>|||Thanks for the response, Meryl.

Connect to SQL Server dialog

Hi,
Is it possible to avoid the last used server being in Query Analyzer
'Connect to SQL Server' dialog by default(when I click on File/Connect
in Query Analyzer) - I don't want to apply 'truncate table' scripts to
a production server by mistake!
Thanks<polinaskulski@.aol.com> wrote in message
news:1120572207.464620.272820@.g49g2000cwa.googlegr oups.com...
> Hi,
> Is it possible to avoid the last used server being in Query Analyzer
> 'Connect to SQL Server' dialog by default(when I click on File/Connect
> in Query Analyzer) - I don't want to apply 'truncate table' scripts to
> a production server by mistake!
> Thanks

I don't think that's possible - if you're concerned about running scripts in
the wrong place, then you can reference @.@.SERVERNAME in your scripts, or
always begin a transaction and require a manual COMMIT or ROLLBACK. Another
option is to use a dedicated administrator account for deployments to
production servers.

But all those approaches have drawbacks as well, and in the end there's no
catch-all substitute for being careful about what you're doing.

Simon