See which SQL Server Agent jobs overlap, which run longer than normal and what failed, across all your servers.
The History view: every run of every job in the last 24 hours, on one timeline. Screenshot of a development build with sample data.
Job Activity Monitor shows one server and the last run. The history sits in msdb with dates and durations packed into integers. These are the questions that take hours to answer by hand.
Schedules are set one job at a time, so nobody sees them together. Backups, index maintenance and the nightly load end up in the same half hour, and each of them gets slower.
A fixed threshold of an hour says nothing about a job that normally takes four minutes and now takes twenty. Every job is measured against its own history.
What ran when, how long it took and how it ended, as a timeline you can read at a glance, with the failing step and its message one click away.
Seven days of runs laid over one 24-hour axis. The peaks show when the server is busiest and how many jobs run at once. Per job you see the schedule as a ghost and what really ran on top of it.
Only the exceptions carry colour: a run that overlaps another job, one that ran longer than its norm, a failure, a start that was not on the schedule.
For every job a baseline from its successful runs: median, 95th percentile, longest run and the trend of the last runs. A run is flagged when it clearly exceeds that norm, and the rule is printed on the page so you can check it.
The same job on several servers can be put side by side, which shows the server where it takes twice as long.
Failed, cancelled and long runs of last night, the last day, week or month. Each row names the failing step and the first line of its message, and counts how often that job had a problem in the period.
Select a row for the full message of every step, ready to copy into a ticket.
Read-only. Agent Job Visibility reads the job tables in msdb and changes nothing: no jobs, no schedules, no objects on your server.
Add your servers on the left, tick the ones you want to see, and every view shows them together with one shared filter.
What is defined where: schedule in plain words, next run, last run and its outcome, typical duration.
What is executing across the estate, for how long, and whether that is normal for that job.
The folded 24-hour picture of schedules and real runs, with the collisions and the busy periods.
Runs that exceeded the job's own norm, and the baseline behind that verdict.
Failures with the failing step and message, for last night or the last 30 days.
The timeline of every run, grouped by server or by job, from 6 hours to everything msdb still holds.
Same look and handling as SQLTreeo Compare, including saved connections with Windows, SQL Server and Microsoft Entra ID authentication.
Designed for Always On, including contained availability groups where the jobs live inside the group. This part is still being tested against real groups.
Read access to the job tables in msdb (db_datareader in msdb) is enough. Nothing is installed on the server.
Agent Job Visibility is in development. There is no download yet, and the price is not set. Leave your address and you get one message when the first version is available.