They say, “April showers bring May flowers.” But what if it doesn’t bring May flowers? What if instead you get May servers getting zapped by lightning? Are you ready?
One of the easiest ways to find out is to check your environment and make sure that you have done as much validation as possible on the environment.
Changes for the checklist are again minor, but they do include the first cumulative update for SQL Server 2012. Be sure to check your environment, as DBAs, it is our jobs to prepare for a total meltdown.
Monthly Checklist
- 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 Server releases 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 CU1
- SQL Server 2012 RTM (Evaluation)
- SQL Server 2008 R2 SP 1 CU6
- SQL Server 2008 R2 SP 1
- SQL Server 2008 R2 CU 13 – Support ends 7/10/2012
- SQL Server 2008 SP 3 CU 4
- SQL Server 2008 SP 3
- SQL Server 2008 SP 2 CU 9 – 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 wait stats.
- Analyze your indexes (via IndexAnalysis)
- 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.
Something Missing?
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.
Related posts: