Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase

Beginning SQL Server - Logins and Users Expand / Collapse
Posted Monday, August 2, 2004 2:59 PM



Group: Administrators
Last Login: Yesterday @ 3:36 PM
Points: 34,362, Visits: 18,572
Comments posted to this topic are about the content posted at

Follow me on Twitter:

Forum Etiquette: How to post data/code on a forum to get the best help
Post #129731
Posted Thursday, January 13, 2005 9:36 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, January 13, 2005 9:45 AM
Points: 1, Visits: 1

Helow! The article is very good and clear, but i need... how i can to do this with commands T-SQL...?? Help me!! thank you!!


Post #155411
Posted Friday, August 3, 2007 11:18 AM



Group: General Forum Members
Last Login: Friday, October 14, 2016 12:07 PM
Points: 1,518, Visits: 3,694
Always good to review the basics. I noticed that the .\ usage in figure 7 was no different than if I click the ... button without it. Am I missing something?

I learned something about security recently that surprised me. The situation is like this. I have a member who is part of a server group. That group has permissions to a database. The specified user cannot connect directly to the database using Query Analyzer. I was a bit surprised, shows an advantage to SQL logins as opposed to Windows login. It's also possible that I didn't do a valid attempt and my result is meaningless.

Also recently I found a use for Deny. I have a reporting database where we want to strictly limit user's access to data. All of these users are in a server group. The ERP system has a set of views provided by the vendor. So we created a second database, created a 'select * from livedb..' set of queries by the same name as the vendor queries and gave the group select permissions to said views.

In the production DB, we denied them select on sysobjects and no select permissions on the vendor views. Apparently by denying the select on sysobjects, you also keep them from running sp_helptext on the views, so they can't see what the code is behind the vendor views.

Knowledge is of two kinds. We know a subject ourselves or we know where we can find information upon it. --Samuel Johnson
Post #387874
Posted Thursday, February 4, 2010 7:44 PM

SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Tuesday, November 15, 2016 1:42 PM
Points: 257, Visits: 130
Steve, excellent post on logins/users! Do you have an updated 2005/2008 version of this? Any help would be greatly appreciated. Thanks!

Post #860116
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse