The Utility Database

  • Chris Shaw


Time and time again, I have been able to use my own custom database, named the utility database, to solve problems. This has shortened troubleshooting times by supplying additional insight into what the system has been doing historically, and what the system is doing now. The utility database has reduced my repetitive and time-consuming tasks, such as reviewing the error logs, by automating and using SQL Server Reporting Services (SSRS) to send reports on a daily basis to my e-mail. When you are able to record database history, it makes it much easier for you to identify certain database patterns, such as growth. The additional data eases the ability to forecast key issues, such as performance degradation or the volume of disk space required when new hardware needs to be ordered.


Current Health Processor Utilization Page Count Cate Gory Create Procedure 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Copyright information

© Bradley Ball, TJay Belt, Glenn Berry, Jes Borland, Carlos Bossy, Louis Davidson, Jeremy Lowell, Ben DeBow, Grant Fritchey, Wendy Pastrick, Kellyn Pot’vin, Jonathan Gardner, Jesper Johansen, Mladen Prajdić, Herve Roggero, Chris Shaw, Gail Shaw, Jason Strate 2012

Authors and Affiliations

  • Chris Shaw

There are no affiliations available

Personalised recommendations