What is a trusted connection in terms of SQL Server 2005 (Trusted vs Windows Auth)?
A trusted connection is used if you're connecting to the database without providing a user name and password. For example, if you are connecting via a Data Source Name, and the DSN contains the user ID you're using to connect, then your trusted connection is true.
3.1 Trusted Connection"Database=DatabaseName" specifies that DatabaseName is the name of the data source. "Trusted_Connection=Yes" specifies that a user account<2> is used to establish this connection.
A trusted context is a database object that defines a trust relationship for a connection between the database and an external entity such as an application server. The trust relationship is based upon the following set of attributes: System authorization ID: Represents the user that establishes a database connection.
Configuring Microsoft SQL Server trusted connections on UNIXProvide the Windows service user name and password in the Microsoft SQL Server connection properties. Select the provider type as ODBC. Select the Use DSN check box. Click OK to create the connection.
A trusted connection is the same thing as using Windows Authentication in SQL Server 2005. Authentication is done by the domain, and authorization is handled by SQL Server.
SQL Server can also use its own logins, such as the sa
user. These are both authenticated and authorized by SQL Server. They are only viable if SQL Server is run in Mixed Authentication Mode.
MSDN has a good article about choosing the right Authentication Mode. It's a good primer.
A Trusted connection means Windows Authentication (i.e. a Windows login).
SQL Server has two Authentication modes: Mixed and Windows Authentication Mode.
Mixed has the option of SQL server logins (username and password) and Windows Authentication.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With