This article has a T-SQL function to detect the SQL Agent job state.  Read more...

will create jobs script for backup or DR purposes to install on another server.  Read more...

This script lists the name, running and success status, last executed/currently executing step name, Average and Last duration, next run time and other related information about Jobs.  Read more...

Continuing with his series on monitoring your SQL Servers, David Bird now looks a a way to fin those long running, active jobs.  Read more...

Read more...

The Replication infrastructure in SQL Server is implemented using SQL Server Agent to execute the various components involved in the form of a job (e.g. LogReader agent job, Distribution agent job, Merge agent job) SQL Server jobs execute a binary executable file which is basically C++ code.  Read more...

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...

Find all Job Parent/Child Relationships and related DTSConfig file locations for each step.  Read more...

This trigger will notify the existing email operator of the job with detailed job step information.  Read more...

SQL Server Agent jobs are made up of a series of one or more Job Steps. A job step is assigned to a specific job subsystem, which identifies the kind of work the job step is going to perform. Each job step runs in a separate security context, although each job also has an owner that determines who can modify the job.  Read more...

I needed to run an ssis package / job on many dates that were not consistent and initially started creating dozens of job schedules before coming up with this idea...  Read more...

This script create Job and backup the database.This job backup the database.This job is scheduled for particular time.   Read more...

The system stored procedure sp_start_job is a very useful T-SQL command that starts a SQL Agent job. The problem with this is that it starts the job and it doesn't wait until the job is finished and sometimes I want to start a job and wait until the job is finished and move on to another job or task that depends on the result of the previous job.  Read more...

In a previous tip, the tip reviewed several steps for a better and improved environment for scheduled jobs. I am totally convinced with the recommendations and want to implement these for my scheduled jobs. To make this easier, I want to create a template so I can produce a suitable and reliable way of updates for my production server. In this tip I provide a step by step exercise to perform on a test server to prepare the customized and tested scripts to run on the production server.  Read more...

The provided SSIS package contains a single script task that will script all SQL Server 2000/2005/2008 Agent Jobs into individual files.  Read more...

Similar to many other Job History scripts, but unique in that it has a timeline.  Read more...

With this view you can obtain last failed job steps without using visual interface.  Read more...

Continuing with his series on monitoring your SQL Servers, David Bird now looks a a way to fin those long running, active jobs.  Read more...

This script deletes the entries from table "change log entries" for a period specified by a parameter.  Read more...

This script will break job schedules down into a readable format (msdb.dbo.sysschedules)  Read more...