Abstract
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.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Rights and permissions
Copyright information
© 2012 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
About this chapter
Cite this chapter
Shaw, C. (2012). The Utility Database. In: Pro SQL Server 2012 Practices. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4302-4771-5_6
Download citation
DOI: https://doi.org/10.1007/978-1-4302-4771-5_6
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4302-4770-8
Online ISBN: 978-1-4302-4771-5
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books