|
|
Posted by aj on 10/15/07 14:46
A few service stop/start/restart questions on SQL Server 2005 SP2, which
I'll call SQLS.
It looks as if there are *potentially* 6 ways to start/stop SQLS
Services like the engine itself, integration services, reporting
service, Agent..
-SQLS Configuration Manager
-SQLS Surface Area Configuration (for Services and Connections)
-Mgmt Studio Local (on server)
-Mgmt Studio Remote (on client)
-Windows Control Panel->Admin Tools->Services
-Command Prompt (ala net start MSSQLSERVER)
By policy, I am /not/ Administrator on the server. But I am SysAdmin
role in SQLS. I have had various levels of success starting/stopping
services in the ways listed above. In some I get Access denied, and in
others I get no msg and it simply doesn't work.
Is there some special non-Admin OS group I need to be in to start/stop
services? Is this handled differently in the different interfaces
listed above?
It seems like my best success for starting/stopping the engine and Agent
is in /local/ Mgmt Studio, but /not/ remote Mgmt Studio - the options
are greyed out on a remote client. Is this by design? Is it a SQLS
bug?
I'm sure I'm not the only SQLS DBA who does not have Admin rights on his
server who wants to start/stop services. Generally speaking, how is
this intended to work?
Any help appreciated.
Allen Jantzen
A freshly minted DQLS DBA
Navigation:
[Reply to this message]
|