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

And I think I'm almost there conceptually. I think I just need a few example/confirmations to bring it home.

1) My understanding is that server permissions ( allow a login to gain access to the database server, but they can't perform any actions on the database (such as updating or deleting a table) unless they have database permissions ( Correct?

2) So for example, if a windows group has CONNECT SQL server permissions, the users that are part of that group can only connect to the database and can not perform any database actions (such as updating or deleting a table) unless further specified in the database permissions. Correct?

3) If someone had database permissions and not server permissions, then that would be useless, right? Since they couldn't connect (or login).

share|improve this question
  1. Unless you make them a sysadmin (or grant them other system-wide privileges), pretty much. It depends on what permissions you've granted to public on the database itself.
  2. Assuming that the group and/or group members do not have other permissions on the database, pretty much.
  3. Pretty much, yeah.
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.