Re: SQL Server and ODBC connection strings question
- From: Sue Hoegemeier <Sue_H@xxxxxxxxxxxxx>
- Date: Thu, 11 May 2006 13:08:31 -0600
In this connection string, you are setting the
authentication 3 times and using two different
authentication methods.
If you wan to connect with Windows authentication, you would
use trusted_connection OR integrated security. They do the
same thing. If you are going to use windows authentication,
don't include a user name a password.
So you should have either trusted_connection, integrated
security or supply a user and password. Just one of the
three - you are using all three.
If you are using Windows authentication, there is no
password being sent across the network.
-Sue
On Tue, 2 May 2006 19:28:01 -0700, SteveS
<SteveS@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I have a connection string I use in a communication program I have created
and I'm curious about something.
Here is the string I use:
connection-string="Driver={SQL
Server};Server=localhost;Database=MyDatabase;Uid=MyName;Pwd=MyPassword;trusted_connection=yes;Integrated Security=SSPI;"
Is it possible to encrypt the password? If I'm using Integrated Security,
is the password still transmitted as clear text? My ultimate goal is to get
the entire string encrypted before it's sent over the wire to connect to the
DB (if not the entire string, I'd really like to NOT have the password set in
clear text). Is this possible - and if so, how?
Thanks,
.
- Prev by Date: SQL Server 2k5 Local and Remote connections
- Next by Date: Can't Kill Process
- Previous by thread: SQL Server 2k5 Local and Remote connections
- Next by thread: Can't Kill Process
- Index(es):
Relevant Pages
|