Errors and events

Errors and events#

This section contains description of selected error messages.

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

Attribute	Description
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.
Severity	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.
State	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.

When a statement fails inside a connected data source rather than in Querona itself, Querona reports the source’s own diagnosis:

SQL Server family sources (SQL Server, Azure SQL) - the error number, severity, state and line number the source raised are reported unchanged. A client sees the same number SQL Server would raise for the same statement, for example 2627 for a primary key violation, 515 for a NULL in a non-nullable column or 8115 for an arithmetic overflow.
Every other source - the failure is reported as error number 7399 with severity 16, together with the message the source produced. This mirrors the number SQL Server reports when a query against a linked server fails at the remote server. Querona does not translate a source’s native error numbers into SQL Server’s numbering, so a client that switches on error numbers must read the message text to tell such failures apart.

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

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

Severity level	Description
0-10	Informational messages that return status information or report errors that aren’t severe.
11-16	Indicate errors that can be corrected by the user.
11	Indicates that the given object or entity doesn’t exist.
14	Indicates security-related errors, such as permission denied.
15	Indicates syntax errors in the TSQL command.
16	Indicates general errors that can be corrected by the user.