Bobcares Logo
Search Call 1-800-383-5193 Emergency Contact
Bobcares Logo
Search Call 1-800-383-5193 Emergency Contact
Emergency Contact

How to Change SQL Server Authentication Mode using SSMS

by Nikhath K | Mar 11, 2022 | Latest, Server Management, SQLServer | 0 comments

Change SQL server authentication mode using SSMS with a little help from the experts at Bobcares.

At Bobcares, we offer solutions for every query, big and small, as a part of our Server Management Services.

Let’s take a look at how our Support Team is ready to help customers change SQL server authentication mode using SSMS.

SQL Server supports two authentication modes: Windows Authentication and Mixed Mode. Windows Authentication uses Windows credentials to connect to the server, while Mixed Mode also allows SQL Server logins for applications and users that require SQL authentication. If you need to change SQL Server authentication mode or are looking for how to change SQL Server authentication mode after installation, SQL Server Management Studio (SSMS) provides a simple way to update the setting. In this article, we’ll show you how to change SQL Server authentication mode using SSMS and enable Mixed Mode if required.

An Overview

    • How to Change SQL Server Authentication Mode Using SSMS
    • Prerequisites
    • How to Change Authentication Mode in SQL Server via SQL Server Management Studio
    • Verify the Authentication Mode
    • How to change Authentication Mode in SQL Server via T-SQL Statement
    • Common Issues After Changing the Authentication Mode
    • Security Best Practice

How to Change SQL Server Authentication Mode Using SSMS

Authentication is a process that helps establish a successful connection. SQL Server offers us two different authentication modes in order to connect to the database instances as seen below:

  • Mixed Mode:

This mode offers two different ways to establish a successful database connection. While one uses SQL Server logins at SQL Server layer and the other uses Windows domain user authenticated using active directory, where the login is created as well as mapped on SQL Server instance.

  • Windows Mode:

    This mode offers only one way to establish database connections. We have to map windows accounts on SQL Server before creating database connections. Furthermore, this mode does not offer access to SQL Server logins.

Moreover, the authentication mode configuration takes place during the SQL Server instance installation. However, we can change the SQL Server authentication mode after the installation as well.

Change SQL Server Authentication Mode using SSMS

An additional risk while using Mixed mode is that the encrypted SQL Server Authentication login password has to be passed across the network during the time of the connection. In some cases, the applications tend to store the password at the client.

Subscribe to our newsletter for the latest updates, news, and features.

Prerequisites

If you plan to change SQL Server authentication mode after installation, make sure you have the following before making any changes:

  • Administrative or sysadmin privileges on the SQL Server instance.
  • Access to SQL Server Management Studio (SSMS).
  • Permission to restart the SQL Server service.
  • A maintenance window if you are updating a production server, as restarting the service temporarily disconnects active sessions.

How to Change Authentication Mode in SQL Server via SQL Server Management Studio

We can modify or set authentication mode in SQL Server with the following steps:

  1. First, launch SSMS and connect to the target SQL Server instance.
  2. Then, right-click the server in SQL Server Management Studio Object Explorer, and click Properties.
  3. Next, head to the Security page, to see both authentication modes under Server authentication. We can select any as per our requirement and click Ok.
  4. After that, click Ok when a popup window asks us to restart the SQL Server service.
  5. Finally, right-click the server in Object Explorer and click Restart. In case SQL Server Agent is also running, we have to restart it as well.

In case we are switching to Mixed mode from Windows mode, we have to enable SQL Server login sa account as it tends to get disabled in the Windows authentication mode.

According to our Support Team, we can enable the SQL Server login sa account with these steps:

  1. First, head to Object Explorer > Security > Logins and right-click sa, and select Properties.
  2. Then, create and confirm a password for the sa login on the General page.
  3. After that, head to the Login section on the Status page and click Enabled followed by Ok.

Verify the Authentication Mode

After you change the authentication mode in SQL Server, verify that the new setting has been applied successfully.

  1. Connect to the SQL Server instance using SSMS.
  2. Right-click the server name and select Properties.
  3. Open the Security page.
  4. Confirm that the selected authentication mode matches the one you configured.
  5. If Mixed Mode is enabled, test a SQL Server login to confirm that it works as expected.

How to change Authentication Mode in SQL Server via T-SQL Statement

Microsoft offers an extended stored procedure that allows us to change authentication mode in the SQL Server with T-SQL statements. Our Support Techs recommend taking a backup of the Windows registry before running the following script to change authentication mode to Windows mode:

USE [master]
GO
EXEC xp_instance_regwrite N'HKEY_LOCAL_MACHINE',
N'Software\Microsoft\MSSQLServer\MSSQLServer',
N'LoginMode', REG_DWORD, 1
GO

However, if we want to switch to Mixed mode, we have to enable sa login. This can also be done with the following T-SQL statement:

ALTER LOGIN sa ENABLE ;
GO
ALTER LOGIN sa WITH PASSWORD = 'STRONG-PASSWORD' ;
GO

Common Issues After Changing the Authentication Mode

If you cannot change SQL Server authentication mode, one of the following issues could be preventing the update.

Issue Possible Cause Quick Fix
SQL Server login fails SQL Server service was not restarted Restart the SQL Server service.
Login failed (Error 18456) Incorrect login credentials or login disabled Verify the username, password, and login status.
Unable to change the authentication mode Insufficient permissions Sign in using an account with sysadmin privileges.
SQL logins are unavailable Windows Authentication is still enabled Confirm that Mixed Mode is selected and restart the SQL Server service.

Security Best Practice

After you change authentication mode SQL Server, follow these practices to help protect your server.

  • Use Windows Authentication whenever it meets your application requirements.
  • Enable Mixed Mode only when SQL Server logins are required.
  • Create strong passwords for SQL Server accounts.
  • Disable or remove SQL logins that are no longer in use.
  • Review login permissions regularly and follow the principle of least privilege.

[Looking for a solution to another query? We are just a click away.]

Conclusion

Now that you know how to change SQL Server authentication mode, you can update the server settings through SSMS, restart the SQL Server service, and verify that the new authentication mode is active. If your applications require SQL logins, you can also change SQL Server to Mixed Mode authentication by following the same process.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

Related posts:

    1. SQL Server Error 35206 – How to resolve
    2. Session Timeout for Availability Group Replica – How to modify
    3. Export large SQL Server query result to .txt file | Top 5 methods
    4. How to change SQL Server database Autogrowth settings

Submit a Comment Cancel reply

Your email address will not be published. Required fields are marked *

Recent Posts

  • Building a Secure GitOps-Based Kubernetes Delivery Pipeline for Modern Cloud Applications
  • The Secret to High Availability : AWS ELASTIC LOAD BALANCING (ELB)
  • How Load Balancers Work: HAProxy, Nginx, and Cloudflare
  • A Beginner’s Guide to KVM Virtualization 
  • What Is Proactive Monitoring? A Complete Guide

Categories

  • Advanced Vulnerability
  • AI Services
  • AI Support
  • AIOps
  • Amazon Web Services (AWS)
  • Apache
  • API Integration
  • Application Development
  • Azure
  • Cloud Cost Optimization
  • Cloud Management
  • Cloud-Native Application
  • Cloudflare
  • cPanel
  • cPanel migration
  • Cyberpanel
  • DDoS
  • Development Service
  • DevOps
  • DevOps Consulting
  • DevSecOps
  • Digital Transformation
  • DigitalOcean
  • DirectAdmin
  • Docker
  • Drupal
  • Ecommerce
  • Filezilla
  • FTP
  • Google cloud platform
  • HAProxy
  • Headless CMS Integration
  • Hosting Support
  • IIS
  • Infrastructure Management & Optimization
  • Kubernetes
  • KVM
  • Laravel
  • Latest
  • Linode
  • Litespeed
  • LXC/LXD
  • Magento
  • Mobile App Development
  • MongoDB
  • Moodle
  • MySQL
  • NFS
  • Nginx
  • OnApp
  • Outsourced Support
  • OVH
  • ovirt
  • pfsense
  • Plesk
  • PostgreSQL
  • PowerDNS
  • Product Engineering
  • Proxmox
  • RedHat
  • Redis
  • Sendmail
  • Server Administration
  • Server Management
  • Software Development
  • Software Testing
  • SQLServer
  • Technical Support
  • UI/UX
  • Virtualizor
  • VMware
  • VPN
  • Vulnerability Scanning
  • Vultr
  • Web Development
  • Windows
  • WordPress
  • WordPress Hosting
  • WordPressHA

Subscribe to our newsletter

Footer newsletter

Email sales@bobcares.com | Phone 1-800-383-5193

Product Engineering

  • MVP Build
  • MVP to Scale
  • Product Maintenance

Digital Transformation

  • Process Digitization & Automation
  • Systems Integration & Workflow Orchestration
  • Data Enablement & Decision Support
  • Application & Platform Modernization
  • Transformation Execution & Delivery Enablement

AI Services

  • AI Readiness & Use-Case Discovery
  • AI Integration & Application Enablement
  • Intelligent Automation & AI Workflows

Infrastructure Management

  • Always-On Infrastructure Management
  • Proactive Monitoring & Incident Prevention
  • Cloud Cost Control & Optimization (FinOps)
  • Outsourced IT & End-User Support
  • Managed Infrastructure Execution Support

DevOps & Automation Services

  • CI/CD & Release Automation
  • Infrastructure as Code & Platform Standardization
  • Reliability Engineering & Observability
  • DevSecOps Enablement
Product Engineering +
Web Development MVP to Scale Builds Microservices Architecture Agile & Dev Team Augmentation Mobile Apps Ecommerce UI/UX Design QA & Test Automation
Digital Transformation +
Legacy Modernization Workflow Automation Data-Driven Dashboards CRM / ERP Integration Business Process Re-engineering
AI Services +
AI & Machine Learning AIOps Intelligent Automation Business Intelligence & Analytics AI Installation & Compute
Infrastructure Management +
Cloud Setup Cloud Migration Managed Cloud Services Server & Hosting Cost Optimization Performance Optimization Outsourced Support
DevOps & Automation Services +
CI/CD Setup Kubernetes & Docker Infrastructure as Code Cloud-Native Migration DevSecOps
Cybersecurity & Compliance Services +
Security Hardening VAPT Incident Response Backup & DR

© 2026 Bobcares. All Rights Reserved.

  • Careers
  • |
  • Cookie Policy
  • |
  • GDPR
  • |
  • Privacy Policy
  • |
  • Terms and Service
  • LinkedIn
  • YouTube
  • Instagram
  • Facebook

Preview of the new Bobcares experience
NEW UPDATE
See What’s New
at Bobcares

Discover a faster, clearer view of our services and expertise.


Explore the New Experience
Arrow Right