Home | Big Picture

This report performs a thorough check of your SQL Server and shows the following data. Click on any item to see a report showing more detail.

For thresholds determining whether anything is highlighted in orange or red see Thresholds.

What It ShowsComments
SQL Server version and edition
Physical MemoryAmount of memory installed in the server
Last restart or failoverDate and time of the last server reboot, service restart or cluster failover - whichever is most recent
Database number and sizeIncludes system databases
Mirrored database statusWhether or not all mirrored databases are synchronized
HADR StatusSQL Server 2012 only
Always On HealthSQL Server 2012 only
Database stateAlerts if any databases are offline
Backup statusChecks that full, diff (if applicable) and log backups are up-to-date.
CPUShows the most recent CPU utilization figure from the ring buffer. This is captured every minute
Page life expectancyThe average number of seconds that a database page is expected to stay in the buffer cache before it is flushed to make way for something else. The higher the better
Log flush wait timeThe current wait in milliseconds to flush the log to disk. This should be as low as possible
Whether or not there are any suspect pagesThis should show "All Pages Clean". If not, perform a CHECKDB against the databases and take steps to recover or fix the errors. Use of DBCC CHECKDB and how to recover is beyond the scope of this help page
Longest running processIt is useful to know if there is a runaway process that may need to be terminated. This does not include SQL Agent jobs or the sp_server_diagnostics process.
Active request
Idle sessions
Active requests are normal on a busy system, but a higher number than usual may indicate a problem
Open Tx
Runnable tasks
A larger than normal number of open transactions or runnable tasks may indicate a problem. A high number of open transactions can result in excessive blocking. A high number of runnable tasks may indicate CPU pressure
Longest blocked processShort term blocking is normal. Any process blocked for more than a few seconds should be investigated
Percentage of tempdb in useYou should size tempdb so that it is big enough to handle all normal workloads without auto-growing. A higher than usual percent in use may indicate a misbehaving process
Data reads
Data writes
Excessively high I/O will have an adverse impact on performance. The figure displayed is the average since the last service restart, and is taken from the virtual file stats
Data reads
Log writes
Log writes should be as low as possible - anything more than 5ms indicates a definite problem with I/O. The figure displayed is the average since the last service restart, and is taken from the virtual file stats
Is SQL Agent service running?
Number of failed jobsIgnores disabled jobs
Number of cancelled jobsIgnores disabled jobs
Are there any jobs that are not enabled?
Are there any jobs that are not scheduled?
Are there any long-running jobs?Any job where the last execution (or current if still running) took more than 20% longer than the average of the last 10 successful runs
Is the default trace running?
The number of deadlocks in the past 4 hoursNot SQL Server 2005
The number of failed logins in the past 4 hours
A breakdown of severity 17+ errors in the past 4 hours

For more information see Getting The Most Out Of SQL CoPilot - See The Big Picture

< Home | Quick Start Home | Configuration >