Server Fault is a question and answer site for system and network administrators. 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

Sorry about the title of the post, but I didn't quite know how to explain this. Here's my issue.

I have a SQL Server that I manage. It is in an Active Directory domain and since I'm the domain admin, I have full rights to it.

I would like to "lock down" the server so that other users can create databases, but cannot have access to mine.

Currently, the other users are using a username that has the same rights as SA. The SA account is scheduled for disabling by the end of the year.

Of course they have become very used to creating there own databases and users without any help from me. I would like to lower there rights so that they can keep using there databases and create any usernames that they would need, but would no longer have the rights of the SA account.

Any ideas? Thanks in advance.

share|improve this question

migrated from Oct 11 '09 at 3:14

This question came from our site for professional and enthusiast programmers.

Look in Books Online for the topic on server-level roles; you're describing the dbcreator role, which can create & manage their own databases, but not databases created by others.

share|improve this answer
Bull. "Members of the dbcreator fixed server role can create, alter, drop, and restore ANY database." - A regular user granted the dbcreator role can DELETE ANY database, including databases they do not own, even though they cannot otherwise access them. – Triynko Jan 17 '11 at 22:28

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.