Graphic view of SQL Server Agent job schedules

So before I stumpled upon SQLjobvis, I used to use Microsoft Excel to create charts and graphical views of SQL Server Agent job schedules. All this time I’ve wasted!

With this tool, I can view all agent jobs on a particular SQL Server, I can see the run duration, I can see when they were successful or when they failed and more. The goal I wanted to achieve with this tool was to be able to see agent job schedule clashes. This isn’t even a manual task where I need to look and see where all the schedules are bunched together. It’s a built in feature of this tool, along the date header it is colour coded to show you where your server is most busiest and least busiest. Perfect!

Aside from the above, you are able to filter the agent jobs shown by certain criteria like failed/long running/clashing. You can filter by categories or even hide disabled or inactive jobs. The tool includes customing the date range viewed and other basic settings.

If you’re looking for a lightweight tool that’s easy to use to see an overview of your SQL Server’s Agent job schedule, this is it. Oh, and it’s FREE!


3 thoughts on “Graphic view of SQL Server Agent job schedules

  1. Hey Jacob,

    can you tell me how you implemented your job schedules in Excel? Unofortunately I dont have the server priviliges to use SQLjobvis, so I’m trying to think of a way to visualize the jobs in Excel.

    Thank you.

    Kind regards,
    Daniel

    1. Hi Dan,

      The way I visually implemented SQL Agent job schedules and run durations in Excel was to have the list of jobs in column A, job scheduled start time in column B and average job run duration in column C. Along the top in row 1, I would have the week day names and 24 hour clock with each cell (from memory) representing about 15 mins. I would then colour each cell to represent the job runs and from there I could spot long running jobs, job schedule clashes etc. To even view this I would print this on 4 A3 sheets of paper and tape them together.

      You can see how this process was both time consuming and manual and can become quickly out of date. It’s something I wouldn’t recommend unless as a last resort. If I were you I’d go about asking for the necessary permissions so you can run SQLjobvis, it’s just read access to some system tables (another blog post).

      Hope this helps

Leave a Reply

Your email address will not be published. Required fields are marked *