October 15, 2011 at 3:07 pm
Comments posted to this topic are about the item Stairway to SQL Server Agent - Level 9: Understanding Jobs and Security
January 11, 2012 at 4:04 pm
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.
---------------------------------------------------------------------
January 11, 2012 at 4:06 pm
Yes, unfortunately although these roles exist for the most part you need to be a sysadmin or the job owner to do anything useful.
January 22, 2012 at 9:03 am
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.
January 25, 2012 at 7:54 am
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.
March 13, 2012 at 5:53 am
Excellent article, great job.
qh
April 15, 2014 at 10:42 pm
Would you consider it a defect to have the login change on the service account, but it wouldn't work properly on a restart of the service?
Is there a command line test I can run to see that the Agent is logged in correctly?
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply