quote:
Now, your "correct" answer says that a login is all that's required, and furthermore it indisputedly implies that database permissions are *not* required (since you say that's *not* the right answer).
I think this is a bit of semantics and here's why:
- I can assign anyone a login within SQL Server.
- I don't have to assign any permissions specifically to that login.
- In normal conversation, we don't talk about what rights the guest user has in master and msdb and tempdb when we're talking about what rights a particular login has.
Therefore, this login that I'm using has no explicit rights assigned to it. Again, it's really all wrapped up in the semantics. But consider it from this perspective: if you have a junior DBA and you need to get across to him who has access to @@VERSION, how are you going to explain it? If he/she doesn't have a lot of experience, you're probably just going to say, "If someone has a login to SQL Server, that someone can run SELECT @@VERSION." If you have the time, you'll go into an explanation of the guest user account in master, but if you don't, you'll leave it as the first.
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1
K. Brian Kelley
@kbriankelley