Errors can have different levels of severity. Based on this severity, you may wish to handle the error in different ways (see my articles on TRY..CATCH). In order to determine the severity of an error, Microsoft SQL has provided the ERROR_SEVERITY() function.
This function takes no argument and returns an integer. Check out this example:
BEGIN TRY DECLARE @Number TINYINT, @Result TINYINT SET @Number = 252; SET @Result = @Number + 20; SELECT @Number AS Number, @Result AS Result; END TRY BEGIN CATCH PRINT N'Error Severity: ' + CAST( ERROR_SEVERITY() AS NVARCHAR(100)) END CATCH
Run this and you should see
Error Severity: 16
If you’re not familiar with the levels of severity, please see this chart provided by Microsoft
|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.|
|10||Informational messages that return status information or report errors that are not severe. For compatibility reasons, the Database Engine converts severity 10 to severity 0 before returning the error information to the calling application.|
|11-16||Indicate errors that can be corrected by the user.|
|11||Indicates that the given object or entity does not exist.|
|12||A special severity for queries that do not use locking because of special query hints. In some cases, read operations performed by these statements could result in inconsistent data, since locks are not taken to guarantee consistency.|
|13||Indicates transaction deadlock errors.|
|14||Indicates security-related errors, such as permission denied.|
|15||Indicates syntax errors in the Transact-SQL command.|
|16||Indicates general errors that can be corrected by the user.|
|17-19||Indicate software errors that cannot be corrected by the user. Inform your system administrator of the problem.|
|17||Indicates that the statement caused SQL Server to run out of resources (such as memory, locks, or disk space for the database) or to exceed some limit set by the system administrator.|
|18||Indicates a problem in the Database Engine software, but the statement completes execution, and the connection to the instance of the Database Engine is maintained. The system administrator should be informed every time a message with a severity level of 18 occurs.|
|19||Indicates that a non-configurable Database Engine limit has been exceeded and the current batch process has been terminated. Error messages with a severity level of 19 or higher stop the execution of the current batch. Severity level 19 errors are rare and must be corrected by the system administrator or your primary support provider. Contact your system administrator when a message with a severity level 19 is raised. Error messages with a severity level from 19 through 25 are written to the error log.|
|20-25||Indicate system problems and are fatal errors, which means that the Database Engine task that is executing a statement or batch is no longer running. The task records information about what occurred and then terminates. In most cases, the application connection to the instance of the Database Engine may also terminate. If this happens, depending on the problem, the application might not be able to reconnect.|
Error messages in this range can affect all of the processes accessing data in the same database and may indicate that a database or object is damaged. Error messages with a severity level from 19 through 25 are written to the error log.
|20||Indicates that a statement has encountered a problem. Because the problem has affected only the current task, it is unlikely that the database itself has been damaged.|
|21||Indicates that a problem has been encountered that affects all tasks in the current database, but it is unlikely that the database itself has been damaged.|
|22||Indicates that the table or index specified in the message has been damaged by a software or hardware problem.|
Severity level 22 errors occur rarely. If one occurs, run DBCC CHECKDB to determine whether other objects in the database are also damaged. The problem might be in the buffer cache only and not on the disk itself. If so, restarting the instance of the Database Engine corrects the problem. To continue working, you must reconnect to the instance of the Database Engine; otherwise, use DBCC to repair the problem. In some cases, you may have to restore the database.
If restarting the instance of the Database Engine does not correct the problem, then the problem is on the disk. Sometimes destroying the object specified in the error message can solve the problem. For example, if the message reports that the instance of the Database Engine has found a row with a length of 0 in a nonclustered index, delete the index and rebuild it.
|23||Indicates that the integrity of the entire database is in question because of a hardware or software problem.|
Severity level 23 errors occur rarely. If one occurs, run DBCC CHECKDB to determine the extent of the damage. The problem might be in the cache only and not on the disk itself. If so, restarting the instance of the Database Engine corrects the problem. To continue working, you must reconnect to the instance of the Database Engine; otherwise, use DBCC to repair the problem. In some cases, you may have to restore the database.
|24||Indicates a media failure. The system administrator may have to restore the database. You may also have to call your hardware vendor.|
The value returned by ERROR_SEVERITY() is the input you can use to decide how to react to the error. You could build a handler that switched based on this number. Then simple errors could be ignored, while severe errors could trigger a safe ROLLBACK and report.
If you’d like more details on error handling, please let me know. I’m more than happy to go into whatever level of detail you need to have. I’m here to help!