Error codes#
Error codes are generally on-par with codes used in SQL Server, that Querona emulates. Because of the nature of the emulation and Querona purposes, only a tiny subset of Sql Server error codes gets used.
Below is a list of notable error codes reported by Querona.
Error |
Severity |
Event logged |
Description |
|---|---|---|---|
102 |
15 |
No |
Incorrect syntax near ‘{0}’. |
134 |
16 |
No |
The variable name ‘{0} has already been declared. Variable names must be unique within a query batch or stored procedure. |
174 |
15 |
No |
The {0} function requires {1} argument(s). |
208 |
16 |
No |
Invalid object name ‘{0}’. |
220 |
16 |
No |
Arithmetic overflow error for data type {0}, value = {1}. |
297 |
16 |
No |
The user does not have permission to perform this action. |
529 |
16 |
No |
Explicit conversion from data type {0} to {1} is not allowed. |
911 |
16 |
No |
Database ‘{0}’ does not exist. Make sure that the name is entered correctly. |
1902 |
16 |
No |
Cannot create more than one clustered index on ‘{0}’. Drop the existing clustered index ‘{1}’ before creating another. |
1913 |
16 |
No |
The operation failed because an index or statistics with name ‘{0}’ already exists on ‘{1}’. |
2740 |
16 |
No |
SET LANGUAGE failed because ‘{0}’ is not an official language name or a language alias. |
3701 |
16 |
No |
Cannot {0} the {1} ‘{2}’, because it does not exist or you do not have permission. |
3980 |
16 |
No |
The request failed to run because the batch is aborted, this can be caused by abort signal sent from client, or another request is running in the same session, which makes the session busy. |
8114 |
16 |
No |
Error converting data type {0} to {1}. |
8115 |
16 |
No |
Arithmetic overflow error converting {0} to data type {1}. |
18456 |
14 |
Yes |
Login failed for user ‘{0}’. |
20002 |
14 |
No |
Tabular Data Stream packet size of {0} is not supported. |
20003 |
14 |
No |
User instance cannot be created. |