|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Wednesday, April 03, 2013 12:29 PM
Points: 11,
Visits: 52
|
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Today @ 4:02 PM
Points: 5,269,
Visits: 11,203
|
|
I think its worth noting here that even members of SQAgentoperatorRole cannot modify or delete jobs they do not own.
This limitation unfortunately prevents granting the right to someone to fully manage all jobs without granting them sysadmin.
---------------------------------------------------------------------
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Wednesday, April 03, 2013 12:29 PM
Points: 11,
Visits: 52
|
|
Yes, unfortunately although these roles exist for the most part you need to be a sysadmin or the job owner to do anything useful.
|
|
|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: Friday, April 19, 2013 3:02 PM
Points: 2,768,
Visits: 108
|
|
In past versions of SQL Server, the SQL Server Agent service account needed Windows Administrator rights on the local computer in order to successfully restart the service when it stops unexpectedly (because the SQL Server Service would have to be restarted first). Is that still true in SQL Server 2008? 2012?
Thanks.
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Wednesday, April 03, 2013 12:29 PM
Points: 11,
Visits: 52
|
|
The SQL Server Agent service account will definately need enough rights to restart the service, I just don't know if that's full administrator rights. For some reason this limitation is not mentioned in the considerations for not using an administrative service account in books online.
|
|
|
|
|
SSCommitted
      
Group: General Forum Members
Last Login: Thursday, May 16, 2013 8:24 AM
Points: 1,610,
Visits: 590
|
|
Excellent article, great job.
qh
SQL 2K acts like a spoilt child - you need to coax it round with lollipops.
|
|
|
|