:::: MENU ::::

Severity levels of error messages in SQL Server 2000

  • Aug 02 / 2008
  • 0
dbDigger, Troubleshooting

Severity levels of error messages in SQL Server 2000

The severity level of an error message provides an indication of the type of problem that Microsoft® SQL Server™ 2000 has encountered. You can see all system messages by running following simple query

 FROM master.dbo.sysmessages  

Level 0 and 10

Severity level 0 and 10 messages are informational and indicate problems caused by mistakes in the information you have entered.

Level 11 – 16
Severity levels from 11 through 16 are generated by the user, and can be corrected by the user.

Level 17 – 25
Severity levels from 17 through 25 indicate software or hardware errors. You should inform the system administrator whenever problems that generate errors with severity levels 17 and higher occur. The system administrator must resolve these errors and track their frequency. When a level 17, 18, or 19 error occurs, you can continue working, although you might not be able to execute a particular statement. The system administrator should monitor all problems that generate severity levels from 17 through 25 and print the error log that contains information to backtrack from the error. If the problem affects an entire database, you can use DBCC CHECKDB (database ) to determine the extent of the damage. DBCC may identify some objects that must be removed and will optionally repair the damage. If damage is extensive, the database might have to be restored.

For user defined error messages
When specifying user-defined error messages with RAISERROR, use error message numbers greater than 50,000 and severity levels from 0 through 18. Only system administrators can issue RAISERROR with a severity level from 19 through 25.

For more detailed information you can go to following links



Consult us to explore the Databases. Contact us