SQL Server Management Studio Standard Reports –Database Consistency History: [DatabaseName]

I'm continuing my series on the Standard Reports in SQL Server Management Studio, and today we’re in the database reports. You can find these reports by starting SQL Server Management Studio and right-clicking a database name. From the menu that appears, click the Standard Reports, and then select the title at the top of this post.

I know – I skipped one report, the one entitled Object Execution Statistics [DatabaseName] , but I type these entries in on the bus ride to work in the mornings, and I need to do some setup for that one! I’ll catch it next when I’m in office on a “proper” system.

This report shows information about the DBCC commands you’ve run on your database. The DBCC commands are integral to your database maintenance, because it checks the database for consistency at the physical and logical levels. If you want more information about that, check here.

Even if you haven’t run the DBCC commands, this report will likely have data in it from your Maintenance Plans (more on those here), since they do run the command. If you don’t see any info, you should be concerned!

The first band in the report groups the information by the DBCC Command:

Column Description
Command Text The text of the DBCC command that was run
Login Name The name of the principal that ran the command. If the command was run by a Maintenance Plan, it’s the login name assigned to the job step that ran the DBBCC command
Start Time The time the command started (on the system)
# Errors The number of errors reported by the DBCC output. If it’s anything other than 0, you should investigate
# Errors Repaired Depending on the DBCC Command, the system can automatically repair certain errors. The number of errors that the system can repair depends on the error and the DBCC Command parameters. In any case, you should investigate
Duration The time it took to run the command, in hours, minutes and seconds. It’s not unusual for these numbers to be all zeros on a small system or if the databases are small