View Batch Run

View Batch Run is a right-click menu option accessible in many of the Instances views (Daily Activity, Operation, Instances, Gantt, etc.). When viewing a Batch Run, the system pulls up all the Jobs and Plans that share a common Batch Run ID. As an example, a triggered Plan generates a Batch Run ID. All instances (the Plan and its Jobs) will have their own unique system-assigned Instance ID, but the Plan, since it was triggered first, will be system-assigned a Batch Run ID that the Jobs also inherit. A Batch Run represents all the Plans and/or Jobs that were executed as part of an initial trigger.

 

Note: Technically, even a single Job triggered generates a Batch Run ID.  In this scenario, the Job's Batch Run ID and the Job's Instance ID are the same.

 

The View Batch Run option allows you to see all the instances that were part of the batch run, in the format you select from a dropdown list. The formats include Gantt, List, and Map. When viewing a batch run, you will see the complete context of all Plans or Jobs that were executed as part of the same batch run.

 

In addition to triggering a Plan, batch runs are also generated when using completion triggers A completion trigger provides the ability for a Job or Plan to trigger another Job or Plan after it completes. You can determine which jobs or plans to trigger based on how your Job or Plan completes. For example, you can trigger one set of jobs if your Job completes successfully, and another set if your Job fails. , or when a Job is triggered due to an alert trigger An Alert Trigger provides the ability to trigger a Job or Plan if the alert condition occurs. For example, if a Job fails, an alert (either embedded or using an Alert object) can be configured to trigger another Job.

 

In the image below, the user-right clicked on the SQL Server Plan in the Instances pane, then selected View Batch Run > List.  The results are tabbed in the Main view. The Plan and its two Jobs share the same Batch Run ID. The Jobs have their own instance ID (as per the ID column in the image below). They also inherited the Batch Run ID from the Plan, which is 1121 (you would need to look at the Properties > History of the Jobs to see their Batch Run ID). The Plan's Instance ID and Batch run ID are the same. Notice the Plan is bold to show its position in the Batch run. Whatever object is triggered first is assigned the same Instance ID and Batch Run ID that the other objects inherit.

 

 

In the image below, the Plan's batch run is depicted in the Map format. The green boxes indicate that the Jobs ran successfully.  The down arrow indicates a completion trigger has been configured on SQL Query 1, meaning, upon the successful completion of SQL Query 1, it will trigger SQL Query 2, which is what happened.

 

 

In the image below, the Plan's batch run is depicted in the Gantt format. The Gantt chart depicts the elapsed time horizontally for each instance. Notice the Job SQL Query 1 took less time to run than SQL Query 2, based on the length of the green horizontal bar.