I have been supporting SQL Server for some time now. One of biggest challenge that I have seen people face with troubleshooting is that they are at a loss because they don’t know where to look and what to collect.
If you know what data to collect and how to collect, that’s half your solution. Two reasons for this:
1. Too much unnecessary information can divert you in the wrong direction
2. Troubleshooting becomes much simpler with just the relevant data collection.
Nothing more, nothing less.
So, in this blog we are going to cover two aspects of maintaining SQL Serves:
1. Pro-active work which will help us minimize points of failure and narrow down to the root if a problem does occur
2. Re-active work which involves having the right approach and action plan ready in case a problem does appear
All comments are most welcome.
Two of the resources for Troubleshooting SQL Server Issues which I have found quite helpful at times are:
1. Technet Forums
2. SQL 2005 Practical Troubleshooting: The Database Engine by Ken Henderson (This is a must read. This is same author for Guru’s Guide to SQL Server. This book has inputs from the DEV team for SQL Server)
I used to blog on Blogspot and Live Spaces but currently I’m in the process of migrating my blog over to WordPress!