Hi All,
  I have faced a problem while i was using the sql server authentication connection using SA without password since there was no password was not assigned to SA. But the connection failed saying that the sa is not the part of trusted connection where as it connected by using the Windows authentication. What could be the problem . Please Help!!!

Trusted Connection has no relation to SA or any other users

Always:),
Hovik Melkomian.

Windows Authentication *is* a Trusted Connection.

There are two ways to connect to SQL Server. One is to use SQL Server accounts and passwords. The SA account is an example of such a user account.

The other mechanism is Integrated Security / Windows Security / Trusted Connections (all the same thing). Using that mechanism, your network logon name is used to connect to SQL Server. So, you logon to your workstation and then connect to SQL Server. Your network logon name then needs access to the SQL Server and databases you need to access.

Integrated Security can be easier to manage and is more secure as you're not sending clear text passwords over the wire.

It's recommended to give the SA account a password as soon as possible. Right now, anyone with access to your SQL Server (i.e. they know it's IP address) can access the server with full rights....

Cheers,

Imar


---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.

Thanks for the replies....
To put more information on my problem the system was not in network . It was being done on a test machine which was isolated from the network. Even the login for the sa is failing. Thats exacly my problem.PLease help!!!

Can you define "failing"? When does it fail? From an application? When you use the Enterprise Manager?



---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.

It is failing from the application as well as from the connection builder utility of the ADODC control

Thanking you,

It looks like you SQL Server is set to allow Windows Authentication only.

There are two ways around it:

1. Don't use SQL Server authentication. Do not use the SA account (especially not without a password) but use your domain accounts instead. IMO, this is the preferred way to go.

2. Change SQL Server's authentication method. To do so, follow these steps:
  a. Open the Enterprise Manager
  b. Expand Server Groups and Servers until you see your SQL Server
  c. Right-click your server and choose Properties
  d. Switch to the Security tab and select "SQL Server and Windows"
  e. Follow the instructions (you'll need to restart SQL Server for the changes to take effect).

Now, SQL Server allows SQL Server Authentication and you can log in with your SA account.

Before you change this, consider your setup carefully. Changing the security method with a blank SA password leaves your system vulnerable to abuse. Anyone can access your SQL Server and read, alter or delete any data they want......

Cheers,

Imar


---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.

Thank you Imar, Thank you very much:)
This was the reply i was looking for.