January 10, 2014 at 12:25 pm
All of us have probably encountered generic error messages while looking through the SQL Server logs. I was wondering if anyone had written, in a single white paper, the top ten errors that will usually be network related, the top ten errors that will usually be storage related, the top ten errors that will usually be OS related, and ways to troubleshoot/diagnose these as such with relevant information to be given to your SAN/Network/Windows buddies? Obviously, the actual network/SAN/Windows implementations that we use will influence what errors we receive, but I was wondering if there are specific errors everyone encounters from time to time?
January 10, 2014 at 2:15 pm
PrometheusRising (1/10/2014)
All of us have probably encountered generic error messages while looking through the SQL Server logs. I was wondering if anyone had written, in a single white paper, the top ten errors that will usually be network related, the top ten errors that will usually be storage related, the top ten errors that will usually be OS related, and ways to troubleshoot/diagnose these as such with relevant information to be given to your SAN/Network/Windows buddies? Obviously, the actual network/SAN/Windows implementations that we use will influence what errors we receive, but I was wondering if there are specific errors everyone encounters from time to time?
It has been my experience in 15 years of consulting on SQL Server that the vast majority of stuff you need to deal with, fix, improve, etc. with SQL Server is NOT logged or represented in any way in the error logs.
To answer your question directly I have never come across such a document or blog post.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
January 12, 2014 at 8:48 am
No, nor I. Most of the stuff in the error log is pretty self-explanatory and not usually vague. But, if you are looking for a good getting started book on troubleshooting, Troubleshooting for the Accidental DBA[/url] is a great resource.
----------------------------------------------------
The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood... Theodore Roosevelt
The Scary DBA Author of: SQL Server 2022 Query Performance Tuning, 6th Edition and SQL Server Execution Plans, 3rd Edition
Product Evangelist for Red Gate Software
January 12, 2014 at 11:06 am
TheSQLGuru (1/10/2014)
It has been my experience in 15 years of consulting on SQL Server that the vast majority of stuff you need to deal with, fix, improve, etc. with SQL Server is NOT logged or represented in any way in the error logs.
+1 BILLION! 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply