Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a user that needs to do queries on an SQL Server 2008 database that I administrate. They have rights to edit the data, but I'd rather they weren't able to do it directly against the table (i.e., I'd prefer they'd use the application that they were given).

What I'd like to do is give them a Read Only ODBC connection, and hang an MS Access MDB/ACCDB off of it, and let them query to their heart's content without accidentally "updating" data.

Is there a way to do this, or am I stuck having to create a RO user for them to use, and then threaten them with much pain if they connect using their regular RW account? In which case why not threaten them with much pain for editing data outside of the application?

share|improve this question
I don't know if there's such a thing as "read-only ODBC connection", but it seems to me you could just create a database user with SELECT rights only. – Andriy M Aug 1 '12 at 19:30
  1. Create a user in SQL Server with only the perms you want them to have.
  2. Set up the user ODBC string to use this credential
  3. Profit :)
share|improve this answer

Create a user and give only read-permissions to him

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.