After working on this monthly checklist for over a year, I’ve recently discovered that there isn’t anything that we should be doing with our SQL Server databases. Apparently, the platform is completely and absolutely self-maintaining and provides built-in disaster recovery without any effort on your part. Along with all of these features, you won’t be responsible if something goes wrong. The end users have volunteered to assume all responsibility for the data platform that you manage.
Obviously, everything in the last paragraph is false, but since it’s April Fools day I had to go with the obvious line of B.S. to start this months list of checklist updates. Monthly reviews of your environment are a key way to ensure that the environment is performing as expected. And that, when there are issues, you know about them before they have a chance to become critical problems.
But where do you start with this review, you can check out the SQL Server Monthly Checklist that I provide on this blog. It covers most everything that should be checked. If you see anything missing from that list, please leave a comment on this post.
There are just a couple changes to the checklist since last month, these updates include:
If you have time to take a look at it, the SQL Server 2012 Product Guide to see how you can use SQL Server in your environment.
Is there something missing in this checklist or with the pages that has been overlooked? Any cool links that would aid in the review of your SQL Server environments? If so, leave a comment below and I’ll take a look.