If you work for a company without a Database Administrator, or if you are a new administrator, there may be some common things missing from your database instances that could cause you major problems down the road. In this article by Tim Radney, we learn some of the common things missing when he looks at his customer systems.
A big part of any DBA consultant’s job is helping clients’ workloads run faster. When I get called to help a client, the first thing I do is perform an audit of their instance to get a good baseline. I pull a lot of history from DMVs, log files and system configuration information.
A lot of effort has gone into making this information gathering as light weight as possible because the last thing I want to do is add stress to an already stressed system. Collecting all this data enables me to be able to check the client’s configuration against commonly accepted best practices as well as performance bottlenecks.
Over the past few years I have found that many clients make the same mistakes – missing changing the same settings or missing implementing the same maintenance. Here are a few that I’ve picked from my long list that I think are the most critical and easy to implement:
- DBCC CHECKDB
- Memory settings
- Index maintenance
- MAXDOP and cost threshold for parallelism
- SQL Server Agent alerts