RE: arghh.. can't get .NET to connect to sql server
From: linda deng[MS] (lideng@online.microsoft.com)
Date: 09/23/02
- Next message: Admin: "Re: restrict server access by ip address"
- Previous message: John Bell: "Re: create linked server for an SQL instance failed"
- In reply to: NeverStill: "arghh.. can't get .NET to connect to sql server"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: lideng@online.microsoft.com (linda deng[MS]) Date: Mon, 23 Sep 2002 05:39:05 GMT
Hi Steve,
When accessing the SQL Server, there are two authentication modes. One is
SQL Server authentication, the other is Windows NT authentication. When you
specify the userid and the password in your connection string, it indicates
that you use the SQL Server authentication, so you should specify a
standard account and its password in the string, for example, 'sa'.
You also can specify 'Integrated Security=SSPI' in your connection string
when using OLE DB Provider, or 'Trusted_Connection = yes' when using ODBC
Driver to utilize the 'Windows NT authentication' to access the SQL Server.
In this situation, you don't need to specify any userid or password in your
string. IIS Server will transfer the user account which you logon on to the
machine 'a' to the SQL Server for authentication. For more information or
sample code on the connection string, you can refer to
http://www.able-consulting.com/ADO_Conn.htm.
Sincerely,
Linda Deng
Microsoft Support Engineer
This posting is provided "AS IS" with no warranties, and confers no rights.
- Next message: Admin: "Re: restrict server access by ip address"
- Previous message: John Bell: "Re: create linked server for an SQL instance failed"
- In reply to: NeverStill: "arghh.. can't get .NET to connect to sql server"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
