Summer is beginning to wrap up for those of us in the northern hemisphere and were finally to August. Maybe the use of “finally” is a little much. If you are like me, you likely feel like we got to August too soon. It seems the older I get the less time it takes to get to the end of the year. Too much time is spent with preparing for and cleaning up from events and holidays. The months have become a blur of the time between, rather than the individual days that should be lived fully. At some point, this bustle and bustle will snap and life can become overwhelming.
Sometimes, being a DBA can be much the same way. Instead of enjoying our jobs for the challenges and joys that they can bring, we are instead swamped with preparing for the next disaster or recovering and explaining the last. We need to run less in our jobs, so that we have the time and energy to do the job well. As part of that goal, you should be examining your SQL Server environment with a SQL Server checklist, such as the one provided in this post. If you know that everything is working as it should, there will be fewer “incidents” and less stress on your life as a DBA.
Just a few changes with this months checklist. First, SQL Server 2008 R2 Service Pack 2 has been released. Make sure that you get this in the pipeline and check to see that your platform is up to date with available updates. A link has also been added pertaining to writing case studies of the work that you do. There are fewer better ways to communicate your impact that through a case study on what was done.
- Backup Validation: Check everything involved in the backup process. Are your backups executing as desired? Are the monitoring jobs properly alerting to failures? Have their been any unexpected failures? Have backup duration times changed?
- Recovery Validation: Is everything for your recovery collected and being backed up? Have you practiced restoring at least one of your SQL Server databases from production in the last month?
- SQL Server Updates: Is your SQL Server environment up-to-date? Check each of your instances and review the most recent releases of SQL Server. Make a plan to determine when the most recent updates will be applied. Also, be aware that support for SQL Serverreleases do end at some point. Support for the version of SQL Server that you are currently using may no longer be supported.
- SQL Server 2012 CU2
- SQL Server 2012 RTM (Evaluation)
- SQL Server 2008 R2 SP 2 CU1
- SQL Server 2008 R2 SP 2
- SQL Server 2008 R2 SP 1 CU7 – Support ends 10/8/2013
- SQL Server 2008 R2 SP 1 – Support ends 10/8/2013
- SQL Server 2008 R2 CU 14 – Support ends 7/10/2012
- SQL Server 2008 SP 3 CU 6
- SQL Server 2008 SP 3
- SQL Server 2008 SP 2 CU 11 – Support ends 10/9/2012
- SQL Server 2008 SP 2 – Support ends 10/9/2012
- SQL Server 2008 SP 1 CU 16 – Support ends 10/11/2011
- SQL Server 2008 SP 1 – Support ends 10/11/2011
- SQL Server 2008 CU 10 – Support ended 4/13/2010
- SQL Server 2005 SP 4 CU 3 – Mainstream support ended 4/12/2011
- SQL Server 2005 SP 4 – Mainstream support ended 4/12/2011
- Windows Server:As important as maintain the SQL Server environment, if the operating system is not up to date, then
- Server Health: Check the performance statistics for your server(s). Were there any unexpected items in your event log? How does everything compare to the last baseline?
- Database Health:Check the performance statistics for your database(s). Were there any unexpected items in your SQL Server logs?
- Check Baselines: Are there any variances on the performance counters off of the baseline? Is the baseline still valid?
- Validate Capacity Plan: If you have a capacity plan in place for your environment, check to see that what you had planned for June matches the actuals. Any threshold violations that may require adding capacity?
- Status Report: What do you need to get done before next month? What did you get done this month? After the other tasks, write this all down and send it to your manager.
Is there something missing in this list that you think should be included? Leave a comment and I’ll add it in for next month.