Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Stairway to SQL Server Agent - Step 2: Job Steps and Subsystems Expand / Collapse
Author
Message
Posted Monday, February 14, 2011 10:37 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, July 1, 2015 3:35 PM
Points: 11, Visits: 64
Comments posted to this topic are about the item Stairway to SQL Server Agent - Step 2: Job Steps and Subsystems


Post #1063685
Posted Thursday, January 15, 2015 1:15 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, November 30, 2016 12:19 PM
Points: 203, Visits: 593
It would be nice if sysjobs and other table are mentioned as scripts to accent the name,steps etc.
Post #1651677
Posted Friday, November 11, 2016 12:59 PM
SSC-Enthusiastic

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

Group: General Forum Members
Last Login: Monday, December 5, 2016 11:21 AM
Points: 131, Visits: 291
Earlier today, I was struggling to diagnose a T-SQL job that selects info from a master db table and sends them to an email. I kept getting SELECT permission issues in the error message. I didn't realize that jobs don't always run as the job owner and it was running instead under the SQLServerAgent account, that wasn't setup as a login on SSMS. As soon as I added the SQLServerAgent account it started working just fine.

This was the only job that was all T-SQL rather than PS or CMDExec, so none of my other jobs were failing.
Post #1833965
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse