Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 

SQL Server 6.5 Security Modes

By Alexander Chigrik,

SQL Server 6.5 uses three security modes:

  • Standard
  • Integrated
  • Mixed

The security mode is selected during SQL Server 6.5 installation and can be modified at any time. To change the security modes, you can do the following:

Click Start, Programs, Microsoft SQL Server 6.5 and click SQL Enterprise Manager to run SQL Enterprise Manager from the Microsoft SQL Server 6.5 program group.

Select the server you want to work with, then from the Server menu select SQL Server, Configure and choose the Security Options page.

Set SQL Server 6.5 security mode.

Standard Security

This security mode is used by default. In this case, SQL Server manages its own login validation process for all connections, i.e. SQL Server is wholly responsible for authenticating a user and for enforcing password and login restrictions.

Integrated Security

When it is used, then Windows NT is responsible for managing user connections through its Access Control List (ACL). So the advantage of using Windows NT Integrated Security mode is single-password access to all resources on a Windows NT domain and password aging and encryption across the network.

With Integrated Security, only Multi-Protocol and Named Pipes clients are supported, and only trusted connections are allowed into SQL Server (trusted connections are only available via the Multi-Protocol or via Named Pipes).

Mixed Security

Mixed Security is a combination of the standard and integrated security. In this case, when a user connects to a SQL Server, then SQL Server checks is it a trusted connection or not (checks is the login name matches the user's network username, or if the login name is null). If it is a trusted connection, then SQL Server uses Windows NT authentication, if it is not a trusted connection then SQL Server uses Standard Security (i.e. tried to find the same SQL Server login name and password, as user has passed).

This security mode is usually used when there are many different clients connected to SQL Server, and one of them use trusted connections and other use standard security (SQL Server login and password).

Total article views: 2382 | Views in the last 30 days: 1
 
Related Articles
FORUM

IIS7/2008 to my SQL Server 2000 machine: Not associated with a trusted SQL Server

Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.

FORUM

SQL Server 2005 Permissions/Trust

Having issues with Trust between servers

FORUM

Cannot login to SQL Server with the SQL authentication

"User is not associated with the trusted SQL server connection"

FORUM

SQL security login help!!

no sql logins working, cannot connect to sql server

Tags
security    
sql server 6.5    
 
Contribute

Join the most active online SQL Server Community

SQL knowledge, delivered daily, free:

Email address:  

You make SSC a better place

As a member of SQLServerCentral, you get free access to loads of fresh content: thousands of articles and SQL scripts, a library of free eBooks, a weekly database news roundup, a great Q & A platform… And it’s our huge, buzzing community of SQL Server Professionals that makes it such a success.

Join us!

Steve Jones
Editor, SQLServerCentral.com

Already a member? Jump in:

Email address:   Password:   Remember me: Forgotten your password?
Steve Jones