SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Who should have Sysadmin rights?


Who should have Sysadmin rights?

Author
Message
bkubicek
bkubicek
SSChampion
SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)

Group: General Forum Members
Points: 10254 Visits: 1099
Comments posted to this topic are about the item Who should have Sysadmin rights?
kp 10240
kp 10240
SSC Rookie
SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)

Group: General Forum Members
Points: 31 Visits: 7
I have been using the login as a different user for a few years now. s you are running with a different user you have a different profile. I use that to change the color scheme of my sql management studio so that it is very apparent in that I have more privileges in this environment.
phegedusich
phegedusich
Ten Centuries
Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)

Group: General Forum Members
Points: 1251 Visits: 545
We have a set of firecall IDs, governed by a change management system, that have the necessary rights in production/DR. You can retrieve the password and log in with the firecall only if you have an approved change number or a high-severity incident ticket number. You cannot use these accounts in your day-to-day business.
Len.Geoghegan
Len.Geoghegan
SSC-Enthusiastic
SSC-Enthusiastic (178 reputation)SSC-Enthusiastic (178 reputation)SSC-Enthusiastic (178 reputation)SSC-Enthusiastic (178 reputation)SSC-Enthusiastic (178 reputation)SSC-Enthusiastic (178 reputation)SSC-Enthusiastic (178 reputation)SSC-Enthusiastic (178 reputation)

Group: General Forum Members
Points: 178 Visits: 183
Seems to me that a user should have access with minimum privileges through standard login, and a separate unique account with elevated privileges. No one should share an account, unless there's some way to limit use of that account to one person at a time and track which person had it for how long - with a new, time-limited password for each request. Otherwise it would be difficult to tell who used the SysAdmin account to drop the production database.
Aaron Cutshall
Aaron Cutshall
SSCrazy Eights
SSCrazy Eights (8.3K reputation)SSCrazy Eights (8.3K reputation)SSCrazy Eights (8.3K reputation)SSCrazy Eights (8.3K reputation)SSCrazy Eights (8.3K reputation)SSCrazy Eights (8.3K reputation)SSCrazy Eights (8.3K reputation)SSCrazy Eights (8.3K reputation)

Group: General Forum Members
Points: 8279 Visits: 1361
Len.Geoghegan - Monday, March 11, 2019 7:18 AM
Seems to me that a user should have access with minimum privileges through standard login, and a separate unique account with elevated privileges. No one should share an account, unless there's some way to limit use of that account to one person at a time and track which person had it for how long - with a new, time-limited password for each request. Otherwise it would be difficult to tell who used the SysAdmin account to drop the production database.

Totally agree. I would have normal logins for everyone, then have specific admin accounts for each person that's accountable for admin access. Sharing an account, especially administrative accounts, allows too much anonymity and doesn't hold each individual accountable.



...when ye are in the service of your fellow beings ye are only in the service of your God. -- Mosiah 2:17
cmullican
cmullican
SSC Veteran
SSC Veteran (236 reputation)SSC Veteran (236 reputation)SSC Veteran (236 reputation)SSC Veteran (236 reputation)SSC Veteran (236 reputation)SSC Veteran (236 reputation)SSC Veteran (236 reputation)SSC Veteran (236 reputation)

Group: General Forum Members
Points: 236 Visits: 119
Agree with minimum necessary privileges, but also, in order to avoid accidentally modifying prod instead of dev / test, I find it's useful to use Register Server in SSMS and assign a different status bar color or color family to each sever, depending on the environment. My prod servers have a red status bar -- caution, do not make changes unless deploying; test is orange (since yellow is the default); dev is green. A server that doesn't neatly fit these categories might be cyan. It's not a foolproof system -- assigning colors per DB instead of per-server would help me -- but combined with moving the status bar to the top of the widow, it makes it very easy to know at a glance which server the current SSMS tab is connected to.
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