Database Health Monitor Beta 8.1 Released Today

Today Database Health Monitor Beta 8.1 released.  After the beta 8 release about three weeks ago there were a couple small issues discovered that have been addressed in Beta 8.1

Beta 8.1 was release to fix some obsolete code from a very old beta that causes the application to expire on Feb 1st, 2014, this limitation has now been removed.  Beta 8.1 also added some better error handling. In beta 8 there was a crash found in some configurations where minimizing the app caused a crash.  This has now been fixed.

New Charts


The biggest change in Beta 8 was the rewrite of many of the charts for an improved look and feel.

Please if you are using Beta 8 or older, please update to Beta 8.1.  Download at

Thanks!  Enjoy the product.


Database Health Reports – Historic Waits Report Sneak Preview

Coming in the next beta of the Database Health Report is a new feature called the Historic Reports which installs a small database to track database statistics over time.  This has an extremely light load on the overall database performance, and will allow you to track down details of why the database was slow at a specific point in time.

Here is the current rough version of the Historic waits report for one database.  With this report, you can filter down to specific time frames with different granularity options to find a specific point in time where the system was slow, and from there determine what query or queries were causing the system to be slow.

The new historic waits reports should completely replace and make obsolete the existing waits reports that were included in Beta 1 and Beta 2.  What I love about the new historic waits reporting is that this is something that I could use to make my job easier every day.

For now please download Beta 2 of the Database Health Reports or register on this site and you will be informed when Beta 3 of the Database Health Reports is available.   Beta 2 was cool, but Beta 3 is going to be spectacular.  Beta 3 is schedule for about November 15th, so I have about 3 and half weeks to get all the cool new historic waits monitoring features in for the Beta.  Beta 3 will support monitoring of SQL Server 2005, 2008, 2008R2 and 2012.

-Steve Stedman

Bellingham WA

Now that Database Health Beta 2 is out, whats next…

Now that Beta 2 of the Database Health Project is out, and people are using it, I am going to focus my attention on 2 areas.

  1. Fixing any bugs that are reported in Beta 2 of the Database Health Project.
  2. Adding new features, specifically related to offline monitoring or history data.

Currently all of the reports in the database health project report on what SQL Server can tell you right now.  What happens when somebody reports that the server was slow at 4:00pm yesterday, how can you track that down. Well, the plan if all goes well with the next beta of the Database Health Project there will be a way to configure a database on a monitoring system that will check up on your SQL server occasionally and record any problems.  This will allow you to be able to find out what query or what wait type caused the system to be slow at some point when you weren’t watching the database.

This is going to be very cool!

So far I have the core tracking and monitoring features working, now I just need to work on the reporting so that it is quick and easy to understand the data.

For now, please try out Beta 2 of the Database Health Project, it is a free download.

-Steve Stedman

Finding the contents of the Plan Cache

I often get asked “how do I find the contents of the SQL Server Plan Cache?”   My first response is just use the Database Health Reports and you can get this through a nice user interface.  But if you still want to get at the Plan Cache contents, I use the following query.

SELECT UseCounts,
       DB_NAME(dbid) as DatabaseName,
  FROM sys.syscacheobjects
 WHERE dbid = db_id();

Again, the Database Health Reportsgives you a much better UI presentation of the conents of the plan cache.

Enjoy the query and please try out the Database Health Reports.

Beta 2 of the Database Health Reports Released

Beta 2 of the Database Health Reports has just been released.  The new Beta contains several bug fixes, and several new features.  Here is a breakdown of what is new or changed since the last beta.

New Features

Bug Fixes

  • Performance tuned the Page Reads and Page Writes reports which were having some difficulty on larger databases.
  • Fixed bug with the Plan Cache Report which was only showing data for the master DB originally, now it shows for the appropriate database.
  • Performance tuning on the Table Size Advisor dialog. There is a lot going on with this, it may take some time, but it is faster than before.
  • Performance tuning on the Fragmented Indexes Report.
  • Improved error handling on connection failures such as invalid password or a bad username.
  • Removed backup status for TempDB as this really didn’t make any sense. Why would anyone backup TempDB.

Download the free Beta 2 version and give it a try.

Finding tables that don’t have a clustered index.

Although clustered indexes are not required, and there are many cases where you should not use a clustered index, quite often clustered indexes can be overlooked when creating a table.  This is actually more likely if you are inheriting a database from someone else who didn’t know enough about indexes.  In these cases adding the right clustered index can dramatically increase performance on queries.

As part of the Database Health Reports, I have added the Unclustered Tables report to report on those tables in your database that do not have a clustered index on them.  From that point you can analyze each of those tables and determine if it should be clustered.

Take a look give it a try.   This report will be in Beta 2, which will be available for download on October 1st 2012.