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


Help: restart SQL Services remotely with SSMS without admin rights?


Help: restart SQL Services remotely with SSMS without admin rights?

Author
Message
SQL Admin-337447
SQL Admin-337447
Forum Newbie
Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)

Group: General Forum Members
Points: 4 Visits: 13
I'm trying to allow SQL DBAs to restart SQL Server service remotely through SSMS without giving them local admin rights to the SQL Server. I was able to give them permissions to restart service through GPO. If I give them Remote Desktop permissions to the server (not local admin), they can connect through RDP and restart SQL Server service, (which to me means they have necessary rights on the box), but they can not do it from SSMS - options are grayed out. What am I missing? I tried assigning users Logon as service right with no effect. Is SSMS only checking for local admin rights on the server and not permissions on the services themselves? Any pointers would be greatly appreciated!
Paul White
Paul White
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: 10352 Visits: 11350
SSMS doesn't always do a brilliant job checking what is possible before graying options out.

Of course sometimes it has no way to check the exact permissions required, and so makes a reasonable guess. That is probably what is happening here.

If anyone can explain why the 'export data' option is greyed out on a read-only database though, I'm all ears. :-D



Paul White
SQLPerformance.com
SQLblog.com
@SQL_Kiwi
SQL Admin-337447
SQL Admin-337447
Forum Newbie
Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)

Group: General Forum Members
Points: 4 Visits: 13
So what is a proper way to let SQL DBA restart SQL service remotely? It's hard for me to believe that the only option is to give the local admin - MS is very much into "least privilege"...
Paul White
Paul White
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: 10352 Visits: 11350
My guess would be to give them a work-around set of permissions just sufficient to allow the service to be managed either via SQL Configuration Manager or some hack like an SC.exe batch file.

You could also set up Agent jobs to do this and use the proxy account to give the required permissions.

There are probably a million ways to this actually.

Paul



Paul White
SQLPerformance.com
SQLblog.com
@SQL_Kiwi
SQL Admin-337447
SQL Admin-337447
Forum Newbie
Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)

Group: General Forum Members
Points: 4 Visits: 13
Thanks, Paul. Since it looks like workaround is my only option here, I've opted out for remote desktop access configured through GPO. This way I can apply GPO to the new SQL server and it will give all necessary permissions to RDP in, restart services, and restart the machine.
VEB
VEB
SSC Rookie
SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)

Group: General Forum Members
Points: 25 Visits: 184
From the OS'es point of view, SQL Server is a service; only local admin privs are enough to restart a service.

I had a similar problem with another product, and I was strictly required not to give local admin rights for junior admins. The workaround I had to use was far from elegant, but quick, simple, and kept me from granting excessive privs - configure a share, grant modify rights to the jr.admins for that share, schedule a batch under priveleged account which checks whether there a file in the share; and if so, restart the service and clear the share; then instruct jr.admin to put the file in the share should a problem arise.
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