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

Stairway to SQL Server Agent - Level 9: Understanding Jobs and Security Expand / Collapse
Author
Message
Posted Saturday, October 15, 2011 3:07 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, May 30, 2014 11:41 AM
Points: 11, Visits: 62
Comments posted to this topic are about the item Stairway to SQL Server Agent - Level 9: Understanding Jobs and Security


Post #1190968
Posted Wednesday, January 11, 2012 4:04 PM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 7:18 AM
Points: 5,871, Visits: 12,972
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.


---------------------------------------------------------------------

Post #1234443
Posted Wednesday, January 11, 2012 4:06 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, May 30, 2014 11:41 AM
Points: 11, Visits: 62
Yes, unfortunately although these roles exist for the most part you need to be a sysadmin or the job owner to do anything useful.


Post #1234444
Posted Sunday, January 22, 2012 9:03 AM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Thursday, September 25, 2014 1:21 PM
Points: 3,143, Visits: 139
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.
Post #1239928
Posted Wednesday, January 25, 2012 7:54 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, May 30, 2014 11:41 AM
Points: 11, Visits: 62
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.


Post #1241545
Posted Tuesday, March 13, 2012 5:53 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Monday, September 22, 2014 9:07 AM
Points: 2,405, Visits: 996
Excellent article, great job.

qh


SQL 2K acts like a spoilt child - you need to coax it round with lollipops.
Post #1265828
Posted Tuesday, April 15, 2014 10:42 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Today @ 7:22 AM
Points: 161, Visits: 1,814
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?
Post #1562113
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse