The following describes how to setup a database user with read-only access to the AdventureWorks database.

Using SQL Server Management Studio 2008:

  1. Connect to your database server.
  2. Expand Security > Logins.
  3. Right-click on the user who will be set as having read-only access (in this example "adventureworksro").
  4. Select Properties.
  5. Select User Mapping.
  6. Map the login to the database they will have access to.
  7. Tick the boxes for role membership next to public and db_datareader.
  8. Confirm by clicking OK.
You should get something like the following:
Login Properties - Adventureworksro

Database-level role names



Members of the db_accessadmin fixed database role can add or remove access to the database for Windows logins, Windows groups, and SQL Server logins.


Members of the db_backupoperator fixed database role can back up the database.


Members of the db_datareader fixed database role can read all data from all user tables.


Members of the db_datawriter fixed database role can add, delete, or change data in all user tables.


Members of the db_ddladmin fixed database role can run any Data Definition Language (DDL) command in a database.


Members of the db_denydatareader fixed database role cannot read any data in the user tables within a database.


Members of the db_denydatawriter fixed database role cannot add, modify, or delete any data in the user tables within a database.


Members of the db_owner fixed database role can perform all configuration and maintenance activities on the database, and can also drop the database.


Members of the db_securityadmin fixed database role can modify role membership and manage permissions. Adding principals to this role could enable unintended privilege escalation.

In theory, a user who can do nearly everything but modify access and security permissions:
Database Role Membership - All but Security


+1 Mike K Tuesday, 21st April 2015, 2:31 pm
Thank you very much for the information. As a JR.DBA I need all the help I can get!
+1 Martin K Wednesday, 4th June 2014, 12:24 pm
Thnx voor the explanation great!
+1 Joel L Friday, 25th October 2013, 11:23 am
Hi Fely,

I'm so jealous as we're still on SQL Server 2008 R2. I'm also not 100% sure if the problem happens in v2012 for security reasons. I figure you add users to individual databases and not to the overall database server. The creating user will more than often have db_owner privileges. I can only suggest checking the other databases that this user is not allowed to access and set the db_denydataread er for them...
+2 fely Friday, 25th October 2013, 11:15 am
I created a new login and a new user and I mapped a database in SQL Server 2012. In the login properties in Securables, we selected permissions "deny" for "View any database" for the user to see only the specified database.

The problem is that the user does not see any database.

If I select "Grant" to "View any database", user can see all databases. How can I make the user can see only the specified database?
+1 Coverskin Monday, 30th September 2013, 4:00 pm
Thank you very much for posting and sharing this great article. It is so interesting. I want to know some other information about this site. So please give me this news quickly. I always will be aware of you.
+1 krishna l Thursday, 18th April 2013, 7:44 am
:D wow it works grat
+1 Hadoop m Wednesday, 18th January 2012, 10:06 am
Excellent post.. Keep it up.
+1 Ecommerce D Saturday, 14th January 2012, 8:42 am
That’s such a great post!
+3 Ramu Thursday, 10th November 2011, 7:19 am
Excellent i got more points..

Add comment