Severity Levels

Question

Post reply

Severity Levels

RRJ

SSC Enthusiast

Points: 106
More actions
January 13, 2010 at 12:22 am

#386088

Comments posted to this topic are about the item Severity Levels

Viewing 10 posts - 1 through 9 (of 9 total)

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

OCTom SSChampion Points: 11785 More actions · Answer 1

Thanks for the question. I wonder why anyone would think that errors could be corrected by a user? 😉

Richard Sisk SSCrazy Points: 2727 More actions · Answer 2

I'm confused. The question asks about the severity below 10, yet the link to documentation address the severity level of 10.

So is there a special meaning to severity levels 0-9?

Error messages with a severity level of 10 are informational. Error messages with severity levels from 11 through 16 are generated by the user and can be corrected by the user. Severity levels from 17 and 18 are generated by resource or system errors; the user's session is not interrupted.

Cliff Jones SSChampion Points: 10547 More actions · Answer 3

Richard Sisk (1/13/2010)
I'm confused. The question asks about the severity below 10, yet the link to documentation address the severity level of 10.
So is there a special meaning to severity levels 0-9?
Error messages with a severity level of 10 are informational. Error messages with severity levels from 11 through 16 are generated by the user and can be corrected by the user. Severity levels from 17 and 18 are generated by resource or system errors; the user's session is not interrupted.

This may be a better resource.

http://msdn.microsoft.com/en-us/library/ms164086.aspx

Mike Dougherty Ten Centuries Points: 1112 More actions · Answer 4

skjoldtc (1/13/2010)
Thanks for the question. I wonder why anyone would think that errors could be corrected by a user? 😉

Yeah, we all know errors are generated by users

Lest anyone think I'm simply picking on users, it's careless developers that let errors get all the way to SQL...

SQLRNNR SSC Guru Points: 281334 More actions · Answer 5

Mike Dougherty (1/13/2010)

skjoldtc (1/13/2010)
it's careless developers that let errors get all the way to SQL...

Well, sort-of. Some places have a review process that includes the dba. If an error makes it all the way through in that scenario; it could be a lack of knowledge, or a lack of time, or carelessness. In any of these, it would be all parties involved responsible for the error making it to SQL. And the party responsible for troubleshooting and fixing it would be the DBA. 😉

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events

john.arnott SSChampion Points: 11882 More actions · Answer 6

The 2008 BOL (link provided by Cliff) is moderately ambiguous, don't you think?

The following table lists and describes the severity levels of the errors raised by the SQL Server Database Engine.
Severity level Description
0-9
Informational messages that return status information or report errors that are not severe. The Database Engine does not raise system errors with severities of 0 through 9.
[other levels described in the rest of the table...]

It's a table of "severity levels of errors raised by the ... engine." that tells us what levels 0-9 would indicate, but then says the Datebase Engine does not raise errors with those levels.

Huh?!?!?:w00t:

Cliff Jones SSChampion Points: 10547 More actions · Answer 7

I noticed that also. I think it was written by Steven Wright. "I had a premonition of a flashback."

EDSlayer Old Hand Points: 398 More actions · Answer 8

And yet, the explanation text on the question states:

"This is an informational message that indicates a problem caused by mistakes in the information the user has entered and not actual errors."

Are not "mistakes in the information the user has entered" in fact, something that can be "corrected by the user" by simply re-entering the information correctly? It sure seems to me that we're given two aspects of the full situation in two separate choices here ... informational messages that indicate a place where the user has made a mistake and can (and should) correct their error.

Oh well, if everything were clear-cut and simple many of us would be without jobs! :satisfied:

Peter Trast SSCarpal Tunnel Points: 4392 More actions · Answer 9

john.arnott (1/13/2010)
The 2008 BOL (link provided by Cliff) is moderately ambiguous, don't you think?
The following table lists and describes the severity levels of the errors raised by the SQL Server Database Engine.
Severity level Description
0-9
Informational messages that return status information or report errors that are not severe. The Database Engine does not raise system errors with severities of 0 through 9.
[other levels described in the rest of the table...]
It's a table of "severity levels of errors raised by the ... engine." that tells us what levels 0-9 would indicate, but then says the Datebase Engine does not raise errors with those levels.
Huh?!?!?:w00t:

And then this link http://msdn.microsoft.com/en-us/library/ms164086.aspx goes on to say

"...For compatibility reasons, the Database Engine converts severity 10 to severity 0 before returning the error information to the calling application. "

So the 10's turn into 0's that are not raised??? wow...

Peter Trast
Microsoft Certified ...(insert many literal strings here)
Microsoft Design Architect with Alexander Open Systems