Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 

Content with tags Administration, SQL Server Agent Rss

   Items 1 to 3 of 3   
 

Long Running Jobs Monitor

Script to be executed every 60 minutes as a job to determine long running jobs.  Read more...
By Gregory Ferdinandsen 2013/07/16 | Source: SQLServerCentral.com | Category: administration
Rating: |  Discuss |   Briefcase | 1,337 reads

Never update systems tables directly - a study in Agent job scheduling

It is often recommended that system tables should not be updated directly. Presenting a case in point built around nightly job configuration in order to demonstrate the possible issues with updating system tables directly.  Read more...
By Nakul Vachhrajani 2012/09/17 | Source: SQLServerCentral.com | Category: sql server agent
Rating: |  Discuss |   Briefcase | 4,286 reads

SQL Server Agent Jobs without an Operator

I work in a fairly large and unwieldy SQL Server shop. Our environment is the wild west. I have DBAs and Developers on my team that create SQL Server Agent Jobs all of the time and there is never an operator setup to email anyone based on a failure condition. I know the right solution here is to "tame the wild west" by locking down the environment and setting up a change management process, but I think that is a topic for another day. Can you give me some idea of how to identify the new recently created SQL Server Agent Jobs and Jobs without an operator setup to email us for a failure condition? I would like to receive emails when either of these conditions occur. Check out the solution to this tip to learn how.   Read more...
By Additional Articles 2011/06/03 | Source: MSSQLTips.com | Category: sql server agent
Rating: (not yet rated)  Rate this |   Briefcase | 3,634 reads
   Items 1 to 3 of 3   
 
Tags
best practices (1)    
dba (1)    
jobs (1)    
monitor (1)    
nightly jobs (1)    
system tables (1)