Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SA to be denied Access


SA to be denied Access

Author
Message
apprabhu
apprabhu
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 1
I want to create a database whose owner will be a login having the "Database Creators" Server Role. Take for example the database created is named "market" created by the login "amit" so invariably the dbo for "market" is "amit".
No other user is granted access to this database. The DB is created in Enterprise Manager. Now I want to restrict the sa of the SQL Server from gaining access to this DB.
Can this be done. Is it mandatory that the sa be treated as the "GOD" having access to all the databases in the SQL Server he is the administrator of.


Regards,
Amit Prabhu


Regards,
Amit Prabhu
Steven.
Steven.
Right there with Babe
Right there with Babe (743 reputation)Right there with Babe (743 reputation)Right there with Babe (743 reputation)Right there with Babe (743 reputation)Right there with Babe (743 reputation)Right there with Babe (743 reputation)Right there with Babe (743 reputation)Right there with Babe (743 reputation)

Group: General Forum Members
Points: 743 Visits: 247
Accounts with SA rights have access to the lot. I don't know of a way to restrict sa access

Steven
DeltaKilo
DeltaKilo
SSC Journeyman
SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)

Group: General Forum Members
Points: 75 Visits: 1
Hi Amit,

sa is a member of the SYSADMIN role and this can't be changed. Can you clarify a bit more what you're trying to do. You see, the "owner" will always be a login that is a member of "dbo" database role while the "database creator" is a separate issue. What is the need to restrict the sa from the database

Regards,
DeltaKilo



Steve Jones
Steve Jones
SSC-Dedicated
SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)

Group: Administrators
Points: 36206 Visits: 18751
Can't restrict sa, similar to the inability of restricting the domain admin. what is missing, however, is the auditing ability (or the take ownership tracking) in SQL. I've seen this quite a bit and I hope it gets corrected, in disallowing sysadmins to "read" all data by default.


Steve Jones
steve@dkranch.net

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Steven.
Steven.
Right there with Babe
Right there with Babe (743 reputation)Right there with Babe (743 reputation)Right there with Babe (743 reputation)Right there with Babe (743 reputation)Right there with Babe (743 reputation)Right there with Babe (743 reputation)Right there with Babe (743 reputation)Right there with Babe (743 reputation)

Group: General Forum Members
Points: 743 Visits: 247
You can sort of restrict 'domain admins' by removing the builtin/admin for the admin group (not exactly advisable) as this can cause problems with full text indexing etc.

Steven
Steve Jones
Steve Jones
SSC-Dedicated
SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)

Group: Administrators
Points: 36206 Visits: 18751
There are a few articles on removing admins from SQL. Not too bad in SS2K.

I was more referring to restricting admins on the network,not SQL.

Steve Jones
steve@dkranch.net

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Mkumari
Mkumari
Mr or Mrs. 500
Mr or Mrs. 500 (540 reputation)Mr or Mrs. 500 (540 reputation)Mr or Mrs. 500 (540 reputation)Mr or Mrs. 500 (540 reputation)Mr or Mrs. 500 (540 reputation)Mr or Mrs. 500 (540 reputation)Mr or Mrs. 500 (540 reputation)Mr or Mrs. 500 (540 reputation)

Group: General Forum Members
Points: 540 Visits: 177
sa is the owner of all the objects.But when the user say amit, if he creates the tables you can see him under the owner column in the EM.So, instead of dbo you can see him as the owner of those tables,but you cannot restrict the sa from accessing those objects.
As others have mentioned you can simply restrict buitin\admins accounts from accessing the objects by removing them.



cabby2583
cabby2583
Grasshopper
Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)

Group: General Forum Members
Points: 24 Visits: 1
My understanding of the SA user account is that it should be used sparingly. As in, give it a complex password, lock it up in a safe and use it only in emergencies. If no one knows the password, the account theoretically can't be used to access the server/s.

If you can do the above and make all of your Administrators members of the "sysadmin" fixed server role, will this accomplish what's being discussed? If you need to restrict all Administrators from this specific database, don't assign anyone to the "sysadmin" role. However, this will probably complicate your life as you try to administer your system/s.

Any thoughts on the SA account use, and how much it should be used, or is commonly used?

cabby2583
caballero@mediaone.net
Always Learn!



DeltaKilo
DeltaKilo
SSC Journeyman
SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)

Group: General Forum Members
Points: 75 Visits: 1
Hi Cabby,

you can't restrict access to an sa user or a member of the Sysadmin role. I see where you're coming from but if you remove people from the sysadmin role that removes "God" access on all databases .... so yep, a complication indeed Smile



ckempste
ckempste
SSC Eights!
SSC Eights! (885 reputation)SSC Eights! (885 reputation)SSC Eights! (885 reputation)SSC Eights! (885 reputation)SSC Eights! (885 reputation)SSC Eights! (885 reputation)SSC Eights! (885 reputation)SSC Eights! (885 reputation)

Group: General Forum Members
Points: 885 Visits: 1
Hi

Its not a problem really, the DBA is the DBA and should be GOD when its comes the DB management and administration. To achieve this, only the DBA uses and knows the SA account (in dev/test/prod) and reworks the BUILTIN\Administrators login account to remove sysadmin access or possibly delete it all together and create a new custom version associated with better defined domain and local groups. In the case where mixed mode is used, the same ideas apply.

Dont be bullied into giving away the SA account, it should remain flexible enough to alter its password at any time (ie, dont go embedding it into dts jobs etc), look at it as your super account for emergancies and "dba" fixes only.

Like in oracle with the sys account, its not going away, so they create a "system" account with slightly different privs etc (but still basically king). So manage the DB and the SA account as such.

My big gripe is auditing in SQL-Server, its basically totally crap and needs a lot more time spent on it, including additional triggers for "on login", etc etc for custom jobs.

Cheers

Chris


Chris Kempster
www.chriskempster.com
Author of "SQL Server Backup, Recovery & Troubleshooting"
Author of "SQL Server 2k for the Oracle DBA"
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search