How to change user access mode in MSSQL Server?

MSSQL Server provides a feature to restrict your Database access for users. It can be performed by selecting appropriate access mode for your database. By default, there will be 3 access modes in SQL Server. Single User, Multiple User and Restricted User.

Option 1 : Change User access mode from MSSQL Management Studio 

Following are the steps to change the user access mode in MSSQL Server.

  1. Login to your MSSQL Server using the SQL Management studio.

  2. Right Click on the Database which user access mode you are looking to change and select properties.



  3. Click on Options.



  4. From other options drop-down >> Go to State >> Restrict Access

  5. At Restrict Access Drop-Down, select the option (single_user, multi_user and restricted_user) as per your requirement and click on OK Button.

Option 2 : Change User access mode Using Transact SQL Command 

  1. Login to your SQL Server with MSSQL Management Studio.

  2. Click on New query.



  3. Hit the below query by changing your database name and required user access mode.

    ALTER DATABASE databasename SET user access mode;


  4. Click on Execute Button.

          This is how you can change your user access for your Database.

  • 0 Users Found This Useful

Was this answer helpful?

Related Articles

Choosing Between SQL Server 2012 and SQL Server 2014

If you are running SQL Server 2008 R2, you might be looking to upgrade your SQL server to...

Do you offer SQL schedule job?

Windows Shared HostingWe do not offer SQL server schedule job in our Windows shared hosting...

How to Install Advanced Features on Existing Instance of MS SQL Server?

If you have chosen MS SQL Server to be installed in Windows VPS while placing an order, you'll...

How to Increase the MS SQL Remote Query Timeout?

MS SQL Server has an option called Remote Query Timeout to specify the time (in seconds), a...

How to configure MSSQL server default language configuration option?

Recently, we faced strange issue wherein one of our customers was capturing error messages coming...