Skip to content

Features in Database Health Monitor: Job History, Problem Indexes, and Backup Reports

Features in Database Health Monitor: Job History, Problem Indexes, and Backup Reports

At Stedman Solutions, we are always working to make SQL Server management easier and more effective. Database Health Monitor continues to evolve with new reports and enhancements designed to help SQL Server administrators better understand what is happening across their environments.

Some of the latest additions focus on three critical areas:

  • SQL Server job activity
  • Problematic indexes
  • Backup visibility and reporting

These new features provide clearer insights, faster troubleshooting, and better operational awareness for DBAs managing SQL Server systems of all sizes.

The New Job History Chart

Viewing SQL Server Agent job history inside SQL Server Management Studio has always been somewhat fragmented. The information is there, but it can be difficult to visualize how jobs interact throughout the day.

The redesigned Job History Chart in Database Health Monitor solves that problem by presenting a complete visual timeline of job activity over a 24-hour period.

Each SQL Server Agent job is displayed with:

  • Start times
  • Stop times
  • Duration
  • Visual overlap with other jobs

The report also allows you to compare current job activity against the previous day’s workload, making unusual patterns much easier to spot.

Long-running jobs, scheduling conflicts, and overlapping maintenance tasks become immediately visible.

CPU Heat Map for Better Scheduling

One of the most useful enhancements in the Job History Chart is the built-in CPU heat map displayed across the top of the timeline.

This heat map provides a quick visual representation of CPU utilization throughout the day.

By comparing job execution times against CPU load, DBAs can easily identify situations where:

  • Too many jobs are running simultaneously
  • Maintenance windows overlap with peak workload periods
  • Job scheduling is contributing to resource contention

Instead of guessing when jobs should run, administrators can now use real workload visibility to optimize scheduling decisions.

For larger environments with hundreds or thousands of jobs, filtering options make it easy to focus on specific jobs or categories without getting overwhelmed by unnecessary data.

The Problem Indexes Report

Another major addition is the new Problem Indexes Report.

SQL Server Management Studio allows you to view indexes, but it does not always make it obvious when an index is disabled.

That can create serious problems because disabled indexes:

  • Consume storage space
  • Provide no query performance benefit
  • Can create a false sense of optimization coverage

With the Problem Indexes Report, disabled indexes are immediately visible so DBAs can quickly determine whether they should be re-enabled or removed entirely.

Fill Factor Visibility and Recommendations

The Problem Indexes Report also includes fill factor analysis.

Many SQL Server environments contain indexes configured with fill factors that are unnecessarily low.

For example, a fill factor of 50 percent means each index page is intentionally left half empty.

Years ago, lower fill factors sometimes made sense on spinning disks to reduce page splits. However, in modern environments running on SSD storage, extremely low fill factors often create unnecessary storage waste and additional overhead.

In many situations, a fill factor closer to 90 percent, 95 percent, or even 99 percent is far more efficient.

The report makes it easy to identify indexes with unusually low fill factors and even provides scripts to help correct them quickly.

Improved Backup Reports

Backup visibility is another area receiving major improvements in Database Health Monitor.

The Backup Size Report now provides a much clearer view of how backup sizes change over time.

This includes separate visibility into:

  • Full backups
  • Differential backups
  • Growth trends

Understanding backup growth patterns helps DBAs plan storage requirements and optimize backup strategies more effectively.

The Backup Timeframe Report

Another valuable addition is the Backup Timeframe Report.

This report visually displays when backups are actually occurring across a two-week period.

It becomes very easy to confirm whether backups are running consistently and on schedule.

If there is a noticeable gap—such as missing full backups or interrupted backup chains—the issue stands out immediately.

For example, if a server has gone two weeks without a successful full backup, the report provides a clear visual warning that action is needed right away.

Helping Prevent Problems Before They Become Disasters

These new reports continue the core mission of Database Health Monitor:

Helping SQL Server administrators identify problems early before they turn into outages, performance crises, or failed recovery situations.

Whether you are troubleshooting blocking, optimizing indexes, balancing workloads, or validating backups, these tools are designed to provide faster insight with less manual effort.

Download Database Health Monitor

If you have not tried Database Health Monitor yet, you can download it for free at:

https://databasehealth.com

SQL Server Managed Services from Stedman Solutions

If your SQL Server environment needs more than monitoring—such as expert tuning, disaster recovery planning, proactive management, or ongoing operational support—our team at Stedman Solutions can help.

With more than three decades of SQL Server experience, we provide:

  • 24/7 monitoring and alerting
  • Performance tuning
  • Disaster recovery assistance
  • Mentoring and guidance
  • Rapid response when problems occur

Learn more about our SQL Server Managed Services at:

https://stedmansolutions.com/contact/

 

More from Stedman Solutions:

SteveStedman5
Steve and the team at Stedman Solutions are here for all your SQL Server needs.
Contact us today for your free 30 minute consultation..
We are ready to help!

Leave a Reply

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

thirty eight − = twenty eight