Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Help: restart SQL Services remotely with SSMS without admin rights? Expand / Collapse
Author
Message
Posted Tuesday, May 26, 2009 6:15 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, July 19, 2010 9:05 AM
Points: 4, Visits: 12
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!
Post #723700
Posted Wednesday, May 27, 2009 3:31 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Saturday, August 30, 2014 4:20 PM
Points: 11,194, Visits: 11,142
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.




Paul White
SQL Server MVP
SQLblog.com
@SQL_Kiwi
Post #723898
Posted Wednesday, May 27, 2009 7:45 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, July 19, 2010 9:05 AM
Points: 4, Visits: 12
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"...
Post #724095
Posted Wednesday, May 27, 2009 4:09 PM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Saturday, August 30, 2014 4:20 PM
Points: 11,194, Visits: 11,142
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
SQL Server MVP
SQLblog.com
@SQL_Kiwi
Post #724645
Posted Thursday, May 28, 2009 5:00 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, July 19, 2010 9:05 AM
Points: 4, Visits: 12
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.
Post #724935
Posted Saturday, May 30, 2009 4:47 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Monday, January 10, 2011 7:58 PM
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.
Post #726196
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse