Home » CodeProject » SQL Server Authentication

SQL Server Authentication

[MSSQLFUN & Decode ITeS becomes a family of 1500 individuals across the globe. Please join us on
& YouTube.]

We will be discussion SQL Server Authentication and below topics:-

  • What is Authentication?
  • Type of authentication in SQL Server (SQL & Windows)
  • Windows Authentication
  • What is Windows authentication?
  • Advantages & Disadvantages

SQL Authentication

  • What is SQL authentication?
  • Advantages & Disadvantages

SQL Server Authentication Modes

  1. What is Authentication?

Authentication, The process of identity verification of the user. In Laymen terms, Attention is the process to check “Who are you?”. It can be based on user-id & password or token-based or certificate-based. Authentication is the key to allow only authorized users can connect to access the data and system.

Only user with correct authentication details able to connect.

  1. Type of authentication in SQL Server (SQL & Windows)

Microsoft supports 2 types of authentications, SQL, and Windows authentication. For each login created on SQL Server, it should be part of either authentication.

  1. Windows Authentication

Windows Authentication depends on Active Directory (AD) to authenticate users before they connect to SQL. Windows auth use series of encryption to ensure no leak of sensitive data. It is the recommended authentication mode because AD is the best way to manage password policies and user and group access to applications in your organization. User Id and password stored in Active Directory. You can run SQL Server only on Windows Authentication called Windows Authentication Mode.

Advantages of Windows Authentication:

ü All in One Domain: When your environment is on one domain, both DB and application are hosting on the same domain. Windows authentication is the best and secure way of DB communication.

ü Domain Controller: Here, we had Domain Controller to manage logins creation \ modification and authentications.

ü Password Policies: Windows logins must bear with password policies. Windows logins can not skip it. This makes the user password more secure and updated.

ü DBA relief: DBA no more needed to manage users and passwords. This task is completely managed by domain admins in windows auth.

ü Windows Group: Windows give functionality to create groups and that group can be added to SQL server to give access to all users in the group in one go.

Disadvantages of Windows Authentication:

ü No Control: DBA has no control over logins, it completely managed by domain admins.

ü Windows Group: Windows groups has a disadvantage as well because membership of the group is hidden to DBA. DBA will not be aware of who is part of groups or when users added or removed from the group.

  1. SQL Authentication

SQL Server Authentication works by storing usernames and passwords in the “Master” database server. It can be used in situations where Active Directory is not available., but, whenever possible, use Windows Authentication exclusively. You can use SQL Server and Windows Authentication at the same time called Mixed Mode.

You can create multiple users under SQL authentication to provided different users different access as per their requirement.

Advantages of SQL Server Authentication

ü Legacy Application Support: You can keep using your legacy application with support of SQL authentication.

ü Vendor Application Support: Vendor or 3rd Party application which are not built specifically to use SQL Server can be used with SQL Server using SQL authentication

ü Cross Operating System: SQL authentication is best to use when the environment had multiple types of operating systems like Windows, Linux, etc.

ü No Domain \ Workgroup \ Non-Trusted Domain Environment: SQL authentication is best to use while working in No Domain, Workgroup, Non-Trusted Domain Environment where users cannot be authenticated using Windows domain controller.

Disadvantages of SQL Server Authentication:

ü Multiple User Name and Password for Users: Let’s consider a user who needs access to multiple database instances. In SQL authentication, the User will have separate login and password for each instance. This will be difficult to manage and annoying.

ü Multiple User Name and Password for DBAs to Manage: Let consider, You are a team of 5 DBAs and using 50 SQL Server instances. This lead to 250 user ID & Password management for DBA.

ü Enforcing Password Policy: SQL Server logins can be skipped from enforcing password policy. These lead to week passwords and no regular change of password.

ü Application or user pass SQL login and password to connect. This communication can be hacked and user id & passwords can be compromised.

  1. SQL Server Authentication Modes

Based on available authentication types, SQL Server supports 2 types of authentication modes.

  • Windows Authentication Mode:- This is the default one and preferred from Microsoft.
  • Mixed Mode: Mixed mode supported Windows authentication along with SQL authentication. Both types (windows & SQL) logins can work under this model.

How to check the current authentication mode?

Right Click on Server Instance Name in Object Explorer > go to Properties > Security Tab

To change authentication mode, you can change the selection from this screen and click ok. This change needs SQL Service to restart to take into effect.

Reference: Rohit Garg (http://mssqlfun.com/)

You can find and follow MSSQLFUN:-

Subscribe YouTube Channel Decode ITES




Other Linked Profiles:-



Leave a Reply

Join us on Facebook

%d bloggers like this: