SQL Server Troubleshooting

  • 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?

  • 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

  • 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

  • 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.
    "Change is inevitable... change for the better is not".

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)
    Intro to Tally Tables and Functions

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply