SysAdmin and ServerAdmin unable to start/stop or pause services

14 Mar 2006 5:59 PM

tideland

Using mixed mode authentication (SQL 2000), I have a SQL account which has
been granted all of the SQL roles, yet it is unable to stop and start or
pause the database or SQL server agent.

Isn't SQL server supposed to pass on control of these services via it's
identity?

In the SQL 2005 Management Studio the menu items for start stop and pause
are greyed out, and the "tape deck" style icons on the database and SQL
Server Agent are empty circles.

What's going on, this seems like a bug.

14 Mar 2006 6:52 PM

Bryan

The services can start up through a domain account or local admin system
account from the OS. If you have equal permissions as the domain logon
account or are part of the local administrators (if local system account is
used), then you can start and stop the server.

BB_DBA

Show quoteHide quote

"tideland" wrote:

> Using mixed mode authentication (SQL 2000), I have a SQL account which has
> been granted all of the SQL roles, yet it is unable to stop and start or
> pause the database or SQL server agent.
>
> Isn't SQL server supposed to pass on control of these services via it's
> identity?
>
> In the SQL 2005 Management Studio the menu items for start stop and pause
> are greyed out, and the "tape deck" style icons on the database and SQL
> Server Agent are empty circles.
>
> What's going on, this seems like a bug.

15 Mar 2006 10:48 PM

tideland

I believe this was the most accurate answer

Show quoteHide quote

"Bryan" wrote:

> The services can start up through a domain account or local admin system
> account from the OS. If you have equal permissions as the domain logon
> account or are part of the local administrators (if local system account is
> used), then you can start and stop the server.
>
> BB_DBA
>
>
> "tideland" wrote:
>
> > Using mixed mode authentication (SQL 2000), I have a SQL account which has
> > been granted all of the SQL roles, yet it is unable to stop and start or
> > pause the database or SQL server agent.
> >
> > Isn't SQL server supposed to pass on control of these services via it's
> > identity?
> >
> > In the SQL 2005 Management Studio the menu items for start stop and pause
> > are greyed out, and the "tape deck" style icons on the database and SQL
> > Server Agent are empty circles.
> >
> > What's going on, this seems like a bug.

14 Mar 2006 8:48 PM

David Browne

Show quote Hide quote

"tideland" <tidel***@discussions.microsoft.com> wrote in message
news:C225D596-3A5A-412B-A36C-7E1131D18513@microsoft.com...
> Using mixed mode authentication (SQL 2000), I have a SQL account which has
> been granted all of the SQL roles, yet it is unable to stop and start or
> pause the database or SQL server agent.
>
> Isn't SQL server supposed to pass on control of these services via it's
> identity?
>
> In the SQL 2005 Management Studio the menu items for start stop and pause
> are greyed out, and the "tape deck" style icons on the database and SQL
> Server Agent are empty circles.
>
> What's going on, this seems like a bug.

No. Administering services, like rebooting the server, is an OS privilege.

David

15 Mar 2006 6:20 AM

sqlfan

You should be able to stop the server using the shutdown command using the
SQL sysadmin account. However you won't be about to startup the service.

15 Mar 2006 10:44 PM

tideland

I eventually found the answer. A little bit of each response is correct.

Granting a SQL account sysadmin privileges would normally allow that account
to stop and start SQL related services by going through the account which SQL
is running under.

HOWEVER, if the SQL server needs to get at network resources then often it
is given a network account, which in turn may have no rights to stop or start
services.

This is what happened to me.

Thanks for all the responses

Show quoteHide quote

"tideland" wrote:

> Using mixed mode authentication (SQL 2000), I have a SQL account which has
> been granted all of the SQL roles, yet it is unable to stop and start or
> pause the database or SQL server agent.
>
> Isn't SQL server supposed to pass on control of these services via it's
> identity?
>
> In the SQL 2005 Management Studio the menu items for start stop and pause
> are greyed out, and the "tape deck" style icons on the database and SQL
> Server Agent are empty circles.
>
> What's going on, this seems like a bug.

16 Mar 2006 7:37 AM

Tibor Karaszi

> Granting a SQL account sysadmin privileges would normally allow that account
> to stop and start SQL related services by going through the account which SQL
> is running under.

How do you expect to start SQL Server is you don't have permissions, SQL Server has permissions, but
SQL Server isn't running?

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/

Show quoteHide quote

"tideland" <tidel***@discussions.microsoft.com> wrote in message
news:3323B91D-5804-4F6C-A4EC-61C8DB27B236@microsoft.com...
>I eventually found the answer. A little bit of each response is correct.
>
> Granting a SQL account sysadmin privileges would normally allow that account
> to stop and start SQL related services by going through the account which SQL
> is running under.
>
> HOWEVER, if the SQL server needs to get at network resources then often it
> is given a network account, which in turn may have no rights to stop or start
> services.
>
> This is what happened to me.
>
> Thanks for all the responses
>
> "tideland" wrote:
>
>> Using mixed mode authentication (SQL 2000), I have a SQL account which has
>> been granted all of the SQL roles, yet it is unable to stop and start or
>> pause the database or SQL server agent.
>>
>> Isn't SQL server supposed to pass on control of these services via it's
>> identity?
>>
>> In the SQL 2005 Management Studio the menu items for start stop and pause
>> are greyed out, and the "tape deck" style icons on the database and SQL
>> Server Agent are empty circles.
>>
>> What's going on, this seems like a bug.