Errors and events#


This section contains description of selected error messages.

Understanding Errors#

Errors raised by Querona have the attributes described in the following table.



Error number

Each error message has a unique error number.

Error message string

The error message contains diagnostic information about the cause of the error. Many error messages have substitution variables in which information, such as the name of the object generating the error, is inserted.


The severity indicates how serious the error is. Errors that have a low severity, such as 1 or 2, are information messages or low-level warnings. Errors that have a high severity indicate problems that should be addressed as soon as possible.


Some error messages can be raised at multiple points in code. For example, an 1105 error can be raised for several different conditions. Each specific condition that raises an error assigns a unique state code. You can use the state number to determine whether the recorded issue is the same as the error you have encountered.

Procedure name

Is the name of the stored procedure in which the error has occurred.

Line number

Indicates which statement in a batch, stored procedure, trigger, or function generated the error.

Error severities#

When an error is raised by the Querona, the severity of the error indicates the type of problem encountered by Querona.

Levels of severity#

The following table lists and describes the severity levels of the errors raised by the Querona.

Severity level



Informational messages that return status information or report errors that aren’t severe.


Indicate errors that can be corrected by the user.


Indicates that the given object or entity doesn’t exist.


Indicates security-related errors, such as permission denied.


Indicates syntax errors in the TSQL command.


Indicates general errors that can be corrected by the user.