Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SQL Server Troubleshooting


SQL Server Troubleshooting

Author
Message
jprometheusmagnus@outlook.com
jprometheusmagnus@outlook.com
Forum Newbie
Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)

Group: General Forum Members
Points: 3 Visits: 82
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?
TheSQLGuru
TheSQLGuru
SSCertifiable
SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)

Group: General Forum Members
Points: 5957 Visits: 8312
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 at GMail
Grant Fritchey
Grant Fritchey
SSCoach
SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)

Group: General Forum Members
Points: 17586 Visits: 32265
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 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 Query Performance Tuning and SQL Server Execution Plans
Product Evangelist for Red Gate Software
Jeff Moden
Jeff Moden
SSC-Forever
SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)

Group: General Forum Members
Points: 45080 Visits: 39912
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

RBAR is pronounced ree-bar and is a Modenism for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Wink

Helpful Links:
How to post code problems
How to post performance problems
Forum FAQs
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search