Reading the Error Messages is key

Published On: 2009-01-15By:

I have a gripe that I need to air.

I can’t stress this enough.  Actually reading the error messages when there is a problem is key to solving the problems.

Most of the time (I admit, not all the time) SQL Server will give you some very useful information about what to do next.

Recently someone posted the following error message and asked how to resolve it.

Msg 682, Level 22, State 148, Line 1
Internal error. Buffer provided to read column value is too small. Run DBCC CHECKDB to check for any corruption.

Now just by reading this error figuring out the next step should be pretty easy.  Run DBCC CHECKDB and post that information, or better yet after it runs and tells you that there is corruption in your database, follow the instructions that it gives you.  Why should you do this?  Well because when you post this error message on a forum you will be told to go and run DBCC CHECKDB and report back.

Those that answer questions online don’t have any magical power to know what’s happening on your SQL Server.  If you don’t read the errors and follow what they tell you, we are not going to be able to help any beyond that.

My rant now ends.


Contact the Author | Contact DCAC


Globally Recognized Expertise

As Microsoft MVP’s and Partners as well as VMware experts, we are summoned by companies all over the world to fine-tune and problem-solve the most difficult architecture, infrastructure and network challenges.

And sometimes we’re asked to share what we did, at events like Microsoft’s PASS Summit 2015.

Awards & Certifications

Microsoft Partner    Microsoft MVP    Microsoft Certified Master    VMWare Partner    VMWare vExpert
   Best Full-Service Cloud Technology Consulting Company    Insights Sccess Award    Technology Headlines Award    Golden Bridge Gold Award    CIO Review Top 20 Azure Solutions Providers
Share via
Copy link