SQL Server System Errors: 34000 - 35999
List of error messages between 34000 and 35999 in SQL Server 2017.
These error messages are all available by querying the sys.messages catalog view on the master database.
| message_id | severity | is_event_logged | text |
|---|---|---|---|
| 34001 | 16 | 0 | Dialog with queue 'syspolicy_event_queue' has encountered an error: %s. |
| 34002 | 16 | 0 | Dialog with queue 'syspolicy_event_queue' has ended. |
| 34003 | 16 | 0 | Error number %d was encountered while processing an event. The error message is: %s. |
| 34004 | 16 | 0 | Execution mode %d is not a valid execution mode. |
| 34010 | 16 | 0 | %s '%s' already exists in the database. |
| 34011 | 16 | 0 | Specified value for property %s cannot be used with execution mode %d. |
| 34012 | 16 | 0 | Cannot delete %s referenced by a %s. |
| 34013 | 16 | 0 | %s '%s' is referenced by a '%s'. Cannot add another reference. |
| 34014 | 16 | 0 | Facet does not exist. |
| 34015 | 16 | 0 | Policy group %s does not exist. |
| 34016 | 16 | 0 | Invalid target filer: %s. Only filters that restrict the first level below the Server node are allowed. |
| 34017 | 16 | 0 | Automated policies cannot reference conditions that contain script. |
| 34018 | 16 | 0 | Target type "%s" is not a valid target type. |
| 34019 | 16 | 0 | Object "%s" is invalid. |
| 34020 | 16 | 0 | Configuration option "%s" is unknown. |
| 34021 | 16 | 0 | Invalid value type for configuration option "%s". Expecting "%s". |
| 34022 | 16 | 0 | Policy automation is turned off. |
| 34050 | 16 | 0 | %ls |
| 34051 | 16 | 0 | %ls |
| 34052 | 16 | 0 | %ls |
| 34053 | 16 | 0 | %ls |
| 34054 | 16 | 0 | Policy Management cannot be enabled on this edition of SQL Server. |
| 34101 | 20 | 1 | An error was encountered during object serialization operation. Examine the state to find out more details about this error. |
| 34102 | 16 | 1 | An object in serialized stream has version %u but maximum supported version of this class is %u. |
| 34103 | 16 | 1 | Error in formatter during serialize/deserialize. Required to process %d elements but processed only %d elements. |
| 34104 | 16 | 0 | An error was encountered during object serialization operation. The object that failed serialization is %hs. |
| 34901 | 16 | 1 | The global lock manager encountered a severe failure. |
| 35001 | 16 | 0 | Parent Server Group does not exist. |
| 35002 | 16 | 0 | Server type and parent Server Group type are not the same |
| 35003 | 16 | 0 | Cannot move node to one of its children |
| 35004 | 16 | 0 | Could not find server group |
| 35005 | 16 | 0 | An invalid value NULL was passed in for @server_group_id. |
| 35006 | 16 | 0 | An invalid value NULL was passed in for @server_id. |
| 35007 | 16 | 0 | Could not find shared registered server. |
| 35008 | 16 | 0 | Cannot delete system shared server groups. |
| 35009 | 16 | 0 | An invalid value NULL was passed in for @server_type. |
| 35010 | 16 | 0 | An invalid value %d was passed in for parameter @server_type. |
| 35011 | 16 | 0 | The @server_name parameter cannot be a relative name. |
| 35012 | 16 | 0 | You cannot add a shared registered server with the same name as the Configuration Server. |
| 35100 | 16 | 0 | Error number %d in the THROW statement is outside the valid range. Specify an error number in the valid range of 50000 to 2147483647. |
| 35101 | 16 | 0 | One of the SET options FMTONLY or NOEXEC was changes from ON to OFF in a TRY...CATCH block. |
| 35200 | 16 | 0 | Failed to add database '%.*ls' to availability group '%.*ls'. The specified availability group is created with basic functionality and supports %d database. |
| 35201 | 10 | 0 | A connection timeout has occurred while attempting to establish a connection to availability replica '%ls' with id [%ls]. Either a networking or firewall issue exists, or the endpoint address provided for the replica is not the database mirroring endpoint of the host server instance. |
| 35202 | 10 | 0 | A connection for availability group '%ls' from availability replica '%ls' with id [%ls] to '%ls' with id [%ls] has been successfully established. This is an informational message only. No user action is required. |
| 35203 | 16 | 0 | Unable to establish a connection between instance '%ls' with id [%ls] and '%ls' with id [%ls] due to a transport version mismatch. |
| 35204 | 10 | 0 | The connection between server instances '%ls' with id [%ls] and '%ls' with id [%ls] has been disabled because the database mirroring endpoint was either disabled or stopped. Restart the endpoint by using the ALTER ENDPOINT Transact-SQL statement with STATE = STARTED. |
| 35205 | 16 | 0 | Could not start the Always On Availability Groups transport manager. This failure probably occurred because a low memory condition existed when the message dispatcher started up. If so, other internal tasks might also have experienced errors. Check the SQL Server error log and the Windows error log for additional error messages. If a low memory condition exists, investigate and correct its cause. |
| 35206 | 10 | 0 | A connection timeout has occurred on a previously established connection to availability replica '%ls' with id [%ls]. Either a networking or a firewall issue exists or the availability replica has transitioned to the resolving role. |
| 35207 | 16 | 0 | Connection attempt on availability group id '%ls' from replica id '%ls' to replica id '%ls' failed because of error %d, severity %d, state %d. |
| 35208 | 16 | 0 | Availability-group DDL operations are permitted only when you are using the master database. Run the USE MASTER command, and retry your availability-group DDL command. |
| 35209 | 16 | 0 | The %ls operation failed for availability replica '%.*ls', because the backup priority value is outside the valid range. The valid range is between %d and %d, inclusive. Set the backup priority to a value within this range, and retry the operation. |
| 35210 | 16 | 0 | Failed to modify options for availability replica '%.*ls' in availability group '%.*ls'. The specified availability group does not contain an availability replica with specified name. Verify that availability group name and availability replica name are correct, then retry the operation. |
| 35211 | 16 | 0 | The %ls operation is not allowed. The operation attempted to change the configuration of availability replica '%.*ls' to the asynchronous-commit availability mode with automatic failover, which is an invalid configuration. Either change the failover mode to manual or the availability mode to synchronous commit, and retry the operation. |
| 35212 | 16 | 0 | The %ls operation is not allowed by the current availability-group configuration. This operation would exceed the maximum number of %d synchronous-commit availability replicas in availability group '%.*ls'. Change one of the existing synchronous-commit replicas to the asynchronous-commit availability mode, and retry the operation. |
| 35213 | 16 | 0 | The %ls operation is not allowed by the current availability-group configuration. This operation would exceed the maximum number of %d automatic failover targets in availability group '%.*ls'. Change one of the existing synchronous-commit replicas to the manual failover mode, and retry the operation. |
| 35214 | 16 | 0 | The %ls operation failed for availability replica '%.*ls'. The minimum value for session timeout is %d. Retry the operation specifying a valid session-timeout value. |
| 35215 | 16 | 0 | The %ls operation is not allowed on availability replica '%.*ls', because automatic failover mode is an invalid configuration on a SQL Server Failover Cluster Instance. Retry the operation by specifying manual failover mode. |
| 35216 | 16 | 0 | An error occurred while adding or removing a log truncation holdup to build secondary replica from primary availability database '%.*ls'. Primary database is temporarily offline due to restart or other transient condition. Retry the operation. |
| 35217 | 16 | 0 | The thread pool for Always On Availability Groups was unable to start a new worker thread because there are not enough available worker threads. This may degrade Always On Availability Groups performance. Use the "max worker threads" configuration option to increase number of allowable threads. |
| 35218 | 16 | 0 | An error occurred while trying to set the initial Backup LSN of database '%.*ls'. Primary database is temporarily offline due to restart or other transient condition. Retry the operation. |
| 35220 | 16 | 0 | Could not process the operation. Always On Availability Groups replica manager is waiting for the host computer to start a Windows Server Failover Clustering (WSFC) cluster and join it. Either the local computer is not a cluster node, or the local cluster node is not online. If the computer is a cluster node, wait for it to join the cluster. If the computer is not a cluster node, add the computer to a WSFC cluster. Then, retry the operation. |
| 35221 | 16 | 0 | Could not process the operation. Always On Availability Groups replica manager is disabled on this instance of SQL Server. Enable Always On Availability Groups, by using the SQL Server Configuration Manager. Then, restart the SQL Server service, and retry the currently operation. For information about how to enable and disable Always On Availability Groups, see SQL Server Books Online. |
| 35222 | 16 | 0 | Could not process the operation. Always On Availability Groups does not have permissions to access the Windows Server Failover Clustering (WSFC) cluster. Disable and re-enable Always On Availability Groups by using the SQL Server Configuration Manager. Then, restart the SQL Server service, and retry the currently operation. For information about how to enable and disable Always On Availability Groups, see SQL Server Books Online. |
| 35223 | 16 | 0 | Cannot add %d availability replica(s) to availability group '%.*ls'. The availability group already contains %d replica(s), and the maximum number of replicas supported in an availability group is %d. |
| 35224 | 16 | 0 | Could not process the operation. Always On Availability Groups failed to load the required Windows Server Failover Clustering (WSFC) library. Verify that the computer is a node in a WSFC cluster. You will need to restart the SQL Server instance to reload the required library functions. |
| 35225 | 16 | 0 | Could not process the operation. The instance of SQL Server is running under WOW64 (Windows 32-bit on Windows 64-bit), which does not support Always On Availability Groups. Reinstall SQL Server in the native 64-bit edition, and re-enable Always On Availability Groups. Then, restart the SQL Server service, and retry the operation. For information about how to enable and disable Always On Availability Groups, see SQL Server Books Online. |
| 35226 | 16 | 0 | Could not process the operation. Always On Availability Groups has not started because the instance of SQL Server is not running as a service. Restart the server instance as a service, and retry the operation. |
| 35228 | 16 | 0 | The attempt to set the failure condition level for availability group '%.*ls' failed. The specified level value is out of the valid range [%u, %u]. Reenter the command specifying a valid failure condition level value. |
| 35229 | 16 | 0 | The attempt to set the health check timeout value for availability group '%.*ls' failed. The specified timeout value is less than %u milliseconds. Reenter the command specifying a valid health check timeout value. |
| 35230 | 16 | 0 | The specified computer name is either an empty string or is longer than %d Unicode characters. Reenter the command specifying a valid computer name. |
| 35231 | 16 | 0 | The specified server instance name, '%ls', is invalid. Reenter the command specifying a valid instance name. |
| 35232 | 16 | 0 | The specified endpoint URL '%.*ls' is invalid. Reenter the command specifying the correct URL. For information about specifying the endpoint URL for an availability replica, see SQL Server Books Online. |
| 35233 | 16 | 0 | Cannot create an availability group containing %d availability replica(s).tThe maximum number of availability replicas in an availability group %ls is %d. Reenter your CREATE AVAILABILITY GROUP command specifying fewer availability replicas. |
| 35234 | 16 | 0 | Database name '%ls' was specified more than once. Reenter the command, specifying each database name only once. |
| 35235 | 16 | 0 | The system name '%ls' was specified more than once in the REPLICA ON clause of this command. Reenter the command, specifying a different instance of SQL Server for each replica. |
| 35236 | 15 | 0 | The endpoint URL was not specified for the availability replica hosted by server instance '%.*ls'. Reenter the command, specifying the endpoint URL of this instance of SQL Server. |
| 35237 | 16 | 0 | None of the specified replicas for availability group %.*ls maps to the instance of SQL Server to which you are connected. Reenter the command, specifying this server instance to host one of the replicas. This replica will be the initial primary replica. |
| 35238 | 16 | 0 | Database '%.*ls' cannot be added to availability group '%.*ls'. The database does not exist on this SQL Server instance. Verify that the database name is correct, then retry the operation. |
| 35239 | 16 | 0 | The ALTER DATABASE <database-name> SET HADR SUSPEND (or SET HADR RESUME) statement failed on database '%.*ls' of availability group '%.*ls''. Either the availability group does not contain the specified database, or the database has not joined the availability group, or the database has not yet started. Reenter the command after the database is online and has joined the availability group. |
| 35240 | 16 | 0 | Database '%.*ls' cannot be joined to or unjoined from availability group '%.*ls'. This operation is not supported on the primary replica of the availability group. |
| 35242 | 16 | 0 | Cannot complete this ALTER DATABASE <database-name> SET HADR operation on database '%.*ls'. The database is not joined to an availability group. After the database has joined the availability group, retry the command. |
| 35243 | 16 | 0 | Failed to set resource property '%.*ls' for availability group '%.*ls'. The operation encountered SQL Server error %d. When the cause of the error has been resolved, retry the ALTER AVAILABILITY GROUP command later. |
| 35244 | 16 | 0 | Database '%.*ls' cannot be added to availability group '%.*ls'. The database is currently joined to another availability group. Verify that the database name is correct and that the database is not joined to an availability group, then retry the operation. |
| 35246 | 16 | 0 | Failed to create the availability group. A SQL Server instance name could not be validated because the dynamic link library (DLL) file '%ls' could not be located (Windows System Error %d). Verify that the specified server instance exists. If it exists, the DLL file might be missing from the server instance. |
| 35247 | 16 | 0 | Failed to create the availability group. A SQL Server instance name could not be validated because the dynamic link library (DLL) file '%ls' could not be loaded (Windows System Error %d). |
| 35248 | 16 | 0 | The %ls operation is not allowed by the current availability-group configuration. The required_synchronized_secondaries_to_commit %d is greater than the %d possible secondary synchronous-commit availability replicas in availability group '%.*ls'. Change one of the existing asynchronous-commit replicas to the synchronous-commit availability mode, and retry the operation. |
| 35249 | 16 | 0 | An attempt to add or join a system database, '%.*ls', to an availability group failed. Specify only user databases for this operation. |
| 35250 | 16 | 0 | The connection to the primary replica is not active. The command cannot be processed. |
| 35251 | 16 | 0 | This command can be run only on the primary replica. Connect to the primary replica, and retry the command. |
| 35252 | 16 | 0 | The command can only be run on a secondary database. Connect to the correct secondary replica, and retry the command. |
| 35253 | 16 | 0 | Database "%.*ls" is not in the correct state to become the primary database. The log must be restored from the previous primary replica to bring the database out of the reinitializing state. |
| 35254 | 16 | 1 | An error occurred while accessing the availability group metadata. Remove this database or replica from the availability group, and reconfigure the availability group to add the database or replica again. For more information, see the ALTER AVAILABILITY GROUP Transact-SQL statement in SQL Server Books Online. |
| 35255 | 16 | 0 | An attempt to start database '%.*ls' failed because the database is already started and online. |
| 35256 | 16 | 0 | The session timeout value was exceeded while waiting for a response from the other availability replica in the session. That replica or the network might be down, or the command might be misconfigured. If the partner is running and visible over the network, retry the command using correctly configured partner-connection parameters. |
| 35257 | 16 | 0 | Always On Availability Groups Send Error (Error code 0x%X, "NOT OK") was returned when sending a message for database ID %d. If the partner is running and visible over the network, retry the command using correctly configured partner-connection parameters. |
| 35258 | 16 | 0 | Error in the hadron simulator. |
| 35259 | 16 | 0 | Database '%.*ls' is already participating in a different availability group. |
| 35260 | 16 | 0 | During an attempted database recovery, an availability database manager was not found for database id %d with availability group ID %d and group database ID %ls. Recovery was terminated. The most likely cause of this error is that the availability group manager is not running, but the cause could be a metadata error. Ensure that the availability group manager and the WSFC cluster are started, and retry the recovery operation. |
| 35261 | 16 | 0 | Attempt to perform an Always On Availability Groups operation on a system database, '%ls', failed. System databases are not supported by Always On Availability Groups. |
| 35262 | 17 | 1 | Skipping the default startup of database '%.*ls' because the database belongs to an availability group (Group ID: %d). The database will be started by the availability group. This is an informational message only. No user action is required. |
| 35263 | 16 | 0 | During the undo phase, a function call (%ls) to the primary replica returned an unexpected status (Code: %d). Check for a possible cause in the SQL Server error log for the primary replica. If an error occurred on the primary database, you might need to suspend the secondary database, fix the issue on the primary database, and then resume the database. |
| 35264 | 10 | 0 | Always On Availability Groups data movement for database '%.*ls' has been suspended for the following reason: "%S_MSG" (Source ID %d; Source string: '%.*ls'). To resume data movement on the database, you will need to resume the database manually. For information about how to resume an availability database, see SQL Server Books Online. |
| 35265 | 10 | 0 | Always On Availability Groups data movement for database '%.*ls' has been resumed. This is an informational message only. No user action is required. |
| 35266 | 10 | 0 | Always On Availability Groups connection with %S_MSG database established for %S_MSG database '%.*ls' on the availability replica '%.*ls' with Replica ID: {%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}. This is an informational message only. No user action is required. |
| 35267 | 10 | 0 | Always On Availability Groups connection with %S_MSG database terminated for %S_MSG database '%.*ls' on the availability replica '%.*ls' with Replica ID: {%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}. This is an informational message only. No user action is required. |
| 35268 | 16 | 1 | Synchronization of a secondary database, '%.*ls', was interrupted, leaving the database in an inconsistent state. The database will enter the RESTORING state. To complete recovery and bring the database online, use current log backups from the primary database to restore the log records past LSN %S_LSN. Alternatively, drop this secondary database, and prepare a new one by restoring a full database backup of the primary database followed by all subsequent log backups. |
| 35269 | 21 | 1 | Synchronization of a secondary database, '%.*ls', was interrupted, leaving the database in an inconsistent state. The database will be marked SUSPECT. To return the database to a consistent state, restore it from a clean database backup followed by all subsequent log backups. |
| 35270 | 10 | 0 | Received a corrupt FileStream transport message. The '%ls' message section is invalid. |
| 35271 | 16 | 0 | The availability database %ls in availailability group %ls failed to complete a reconfiguration. Refer to the error code for more details. If this condition persists, contact the system administrator. |
| 35272 | 16 | 0 | Either nvalid parameters were supplied for sys.sp_availability_group_command_internal or user does not have permissions to execute this procedure. |
| 35273 | 10 | 1 | Bypassing recovery for database '%ls' because it is marked as an inaccessible availability database. The session with the primary replica was interrupted while reverting the database to the common recovery point. Either the WSFC node lacks quorum or the communications links are broken because of problems with links, endpoint configuration, or permissions (for the server account or security certificate). To gain access to the database, you need to determine what has changed in the session configuration and undo the change. |
| 35274 | 10 | 1 | Recovery for availability database '%ls' is pending until the secondary replica receives additional transaction log from the primary before it complete and come online. Ensure that the server instance that hosts the primary replica is running. |
| 35275 | 16 | 1 | A previous RESTORE WITH CONTINUE_AFTER_ERROR operation or being removed while in the SUSPECT state from an availability group left the '%.*ls' database in a potentially damaged state. The database cannot be joined while in this state. Restore the database, and retry the join operation. |
| 35276 | 17 | 1 | Failed to allocate and schedule an Always On Availability Groups task for database '%ls'. Manual intervention may be required to resume synchronization of the database. If the problem persists, you might need to restart the local instance of SQL Server. |
| 35277 | 16 | 0 | Automatic failover is not supported for distributed availability group replica. |
| 35278 | 16 | 0 | Availability database '%.*ls', which is in the secondary role, is being restarted to resynchronize with the current primary database. This is an informational message only. No user action is required. |
| 35279 | 16 | 1 | The attempt to join database '%.*ls' to the availability group was rejected by the primary database with error '%d'. For more information, see the SQL Server error log for the primary replica. |
| 35280 | 16 | 0 | Database '%.*ls' cannot be added to availability group '%.*ls'. The database is already joined to the specified availability group. Verify that the database name is correct and that the database is not joined to an availability group, then retry the operation. |
| 35281 | 16 | 0 | Database '%.*ls' cannot be removed from availability group '%.*ls'. The database is not joined to the specified availability group. Verify that the database name and the availability group name are correct, then retry the operation. |
| 35282 | 16 | 0 | Availability replica '%.*ls' cannot be added to availability group '%.*ls'. The availability group already contains an availability replica with the specified name. Verify that the availability replica name and the availability group name are correct, then retry the operation. |
| 35283 | 16 | 0 | Availability replica '%.*ls' cannot be removed from availability group '%.*ls'. The availability group does not contain an availability replica with the specified name. Verify that the availability replica name is correct, then retry the operation. |
| 35284 | 16 | 0 | Availability replica '%.*ls' cannot be removed from availability group '%.*ls', because this replica is on the local instance of SQL Server. If the local availability replica is a secondary replica, connect to the server instance that is currently hosting the primary replica, and re-run the command. |
| 35285 | 10 | 0 | The recovery LSN %S_LSN was identified for the database with ID %d. This is an informational message only. No user action is required. |
| 35286 | 16 | 0 | Using the recovery LSN %S_LSN stored in the metadata for the database with ID %d. This is an informational message only. No user action is required. |
| 35287 | 16 | 0 | Always On Availability Groups transport for availability database "%.*ls" failed to decompress the log block whose LSN is %S_LSN. This error can be caused by a corrupt network packet or a compression version mismatch. The database replica has been put into the SUSPENDED state. Resume the availability database. If the error keeps reoccurring, investigate the root cause. |
| 35288 | 16 | 0 | Always On Availability Groups log apply for availability database "%.*ls" has received an out-of-order log block. The expected LSN was %S_LSN. The received LSN was %S_LSN. The database replica has been put into the SUSPENDED state. Resume the availability database. If the error reoccurs, contact Customer Support Services. |
| 35289 | 16 | 0 | Failed to send request for file '%.*ls' to the '%.*ls' primary database for the local secondary database. Resuming the database will be retried automatically. |
| 35290 | 16 | 0 | Failed to wait for completion of file requests from the '%.*ls' primary database for the local secondary database. Resuming the database will be retried automatically. |
| 35291 | 10 | 0 | Failed to acquire exclusive access to the extended recovery fork stack (error %d). If the problem persists, you might need to restart the instance of SQL Server. |
| 35292 | 16 | 0 | An internal error occurred when performing an operation on extended recovery forks. This is an informational message only. No user action is required. |
| 35293 | 16 | 0 | Error in retrieving extended recovery forks from the primary replica. The extended-recovery-fork stack changed while being retrieved by the secondary replica. Retry the operation. |
| 35294 | 16 | 0 | Log backup for database "%.*ls" on a secondary replica failed because a synchronization point could not be established on the primary database. Either locks could not be acquired on the primary database or the database is not operating as part of the availability replica. Check the database status in the SQL Server error log of the server instance that is hosting the current primary replica. If the primary database is participating in the availability group, retry the operation. |
| 35295 | 16 | 0 | Log backup for database "%.*ls" on a secondary replica failed because the last backup LSN (0x%ls) from the primary database is greater than the current local redo LSN (0x%ls). No log records need to be backed up at this time. Retry the log-backup operation later. |
| 35296 | 16 | 0 | Log backup for database "%.*ls" on secondary replica failed because the new backup information could not be committed on primary database. Check the database status in the SQL Server error log of the server instance that is hosting the current primary replica. If the primary database is participating in the availability group, retry the operation. |
| 35297 | 10 | 0 | Log backup for database "%.*ls" on secondary replica created backup files successfully but could not ensure that a backup point has been committed on the primary. This is an informational message only. Preserve this log backup along with the other log backups of this database. t |
| 35298 | 10 | 0 | The backup on the secondary database "%.*ls" was terminated, but a terminate backup message could not be sent to the primary replica. This is an informational message only. The primary replica should detect this error and clean up its backup history accordingly. |
| 35299 | 10 | 1 | Nonqualified transactions are being rolled back in database %.*ls for an Always On Availability Groups state change. Estimated rollback completion: %d%%. This is an informational message only. No user action is required. |
| 35301 | 15 | 0 | The statement failed because a columnstore index cannot be unique. Create the columnstore index without the UNIQUE keyword or create a unique index without the COLUMNSTORE keyword. |
| 35302 | 15 | 0 | The statement failed because specifying sort order (ASC or DESC) is not allowed when creating a columnstore index. Create the columnstore index without specifying a sort order. |
| 35303 | 15 | 0 | The statement failed because a nonclustered index cannot be created on a table that has a clustered columnstore index. Consider replacing the clustered columnstore index with a nonclustered columnstore index. |
| 35304 | 15 | 0 | The statement failed because a clustered columnstore index cannot be created on a table that has a nonclustered index. Consider dropping all nonclustered indexes and trying again. |
| 35305 | 15 | 0 | The statement failed because a clustered columnstore index cannot be created on a view. Consider creating a nonclustered columnstore index on the view, creating a clustered columnstore index on the base table or creating an index without the COLUMNSTORE keyword on the view. |
| 35306 | 15 | 0 | The statement failed because a columnstore index cannot be specified using INDEX specification at the column level. |
| 35307 | 15 | 0 | The statement failed because column '%.*ls' on table '%.*ls' is a computed column. Columnstore index cannot include a computed column implicitly or explicitly. |
| 35308 | 15 | 0 | The statement failed because a columnstore index cannot be a filtered index. Consider creating a columnstore index without the predicate filter. |
| 35309 | 15 | 0 | The statement failed because a columnstore index cannot be created on a sparse column. Consider creating a nonclustered columnstore index on a subset of columns that does not include any sparse columns. |
| 35310 | 15 | 0 | The statement failed because columnstore indexes are not allowed on table types and table variables. Remove the column store index specification from the table type or table variable declaration. |
| 35311 | 15 | 0 | The statement failed because a columnstore index cannot have included columns. Create the columnstore index on the desired columns without specifying any included columns. |
| 35312 | 15 | 0 | The statement failed because a columnstore index cannot be created on a column with filestream data. Consider creating a nonclustered columnstore index on a subset of columns that does not include any columns with filestream data. |
| 35313 | 15 | 0 | The statement failed because specifying FILESTREAM_ON is not allowed when creating a columnstore index. Consider creating a columnstore index on columns without filestream data and omit the FILESTREAM_ON specification. |
| 35314 | 15 | 0 | The statement failed because a columnstore index cannot be created on a column set. Consider creating a nonclustered columnstore index on a subset of columns in the table that does not contain a column set or any sparse columns. |
| 35315 | 15 | 0 | The statement failed because a columnstore index cannot be created in this edition of SQL Server. See Books Online for more details on feature support in different SQL Server editions. |
| 35316 | 15 | 0 | The statement failed because a columnstore index must be partition-aligned with the base table. Create the columnstore index using the same partition function and same (or equivalent) partition scheme as the base table. If the base table is not partitioned, create a nonpartitioned columnstore index. |
| 35317 | 15 | 0 | The statement failed because specifying %S_MSG is not allowed when creating a columnstore index. Consider creating a columnstore index without specifying %S_MSG. |
| 35318 | 15 | 0 | The statement failed because the %S_MSG option is not allowed when creating a columnstore index. Create the columnstore index without specifying the %S_MSG option. |
| 35319 | 15 | 0 | The table option DATA_COMPRESSION is not allowed when a table specifies a clustered column store index. |
| 35320 | 15 | 0 | Column store indexes are not allowed on tables for which the durability option SCHEMA_ONLY is specified. |
| 35321 | 16 | 0 | Table '%.*ls' uses a clustered columnstore index. Columnstore indexes are not supported in this service tier of the database. See Books Online for more details on feature support in different service tiers of Windows Azure SQL Database. |
| 35322 | 16 | 0 | The statement failed because a nonclustered index and the underlying clustered columnstore index must be partition-aligned. Consider creating the nonclustered index using the same partition function and same (or equivalent) partition scheme as the clustered columnstore index. |
| 35323 | 16 | 0 | The statement failed because adding multiple generated value type columns (such as identity and uniqueidentifier types) at once is not supported for columnstore index. Consider adding the generated columns seperately. |
| 35324 | 15 | 0 | The statement failed because specifying SORT_IN_TEMPDB is not allowed when creating a columnstore index without ORDER. Consider creating a columnstore index without specifying SORT_IN_TEMPDB, or use it with ORDER clause. |
| 35325 | 15 | 0 | The statement failed because the definition of a column belonging to clustered columnstore index cannot be changed. Consider dropping the columnstore index, altering the column, then creating a new columnstore index. |
| 35326 | 15 | 0 | The statement failed because a nonclustered columnstore index cannot be reorganized. Reorganization of a nonclustered columnstore index is not necessary. |
| 35327 | 15 | 0 | ALTER INDEX REBUILD statement failed because specifying %S_MSG is not allowed when rebuilding a columnstore index. Rebuild the columnstore index without specifying %S_MSG. |
| 35328 | 15 | 0 | ALTER INDEX REBUILD statement failed because the %S_MSG option is not allowed when rebuilding a columnstore index. Rebuild the columnstore index without specifying the %S_MSG option. |
| 35329 | 15 | 0 | The statement failed because specifying ORDER is not allowed when creating the rowstore index '%.*ls' on table '%.*ls'. Consider creating the rowstore index without specifying ORDER. |
| 35330 | 16 | 0 | %S_MSG statement failed because data cannot be updated in a table that has a nonclustered columnstore index. Consider disabling the columnstore index before issuing the %S_MSG statement, and then rebuilding the columnstore index after %S_MSG has completed. |
| 35331 | 16 | 0 | Cannot use duplicate column names in the ORDER column list. Column name '%.*ls' appears more than once. |
| 35332 | 16 | 0 | Cannot ORDER on more than %d columns. |
| 35334 | 15 | 0 | DBCC DBREINDEX failed because specifying FILLFACTOR is not allowed when creating or rebuilding a columnstore index. Rebuild the columnstore index without specifying FILLFACTOR. |
| 35335 | 15 | 0 | The statement failed because specifying a key list is not allowed when creating a clustered columnstore index. Create the clustered columnstore index without specifying a key list. |
| 35336 | 15 | 0 | The statement failed because specifying key list is missing when creating an index. Create the index with specifying key list . |
| 35337 | 16 | 0 | UPDATE STATISTICS failed because statistics cannot be updated on a columnstore index. UPDATE STATISTICS is valid only when used with the STATS_STREAM option. |
| 35338 | 16 | 0 | Clustered columnstore index is not supported. |
| 35339 | 16 | 0 | Multiple columnstore indexes are not supported. |
| 35340 | 16 | 0 | LOB columns are disabled in columnstore. |
| 35341 | 16 | 0 | The statement failed. A columnstore index cannot include a decimal or numeric data type with a precision greater than 18. Reduce the precision or omit column '%.*ls'. |
| 35342 | 15 | 0 | The statement failed because specifying ORDER is not a valid option for creating the non-clustered columnstore index '%.*ls' on table '%.*ls'. Consider creating the non-clustered columnstore index without specifying ORDER, or create a clustered columnstore index. |
| 35343 | 15 | 0 | The statement failed. Column '%.*ls' has a data type that cannot participate in a columnstore index. |
| 35344 | 16 | 0 | MERGE clause of ALTER PARTITION statement failed because two nonempty partitions containing a columnstore index cannot be merged. Consider an ALTER TABLE SWITCH operation from one of the nonempty partitions on the source table to a temporary staging table and then re-attempt the ALTER PARTITION MERGE operation. Once completed, use ALTER TABLE SWITCH to move the staging table partition back to the original source table. |
| 35345 | 16 | 0 | MERGE clause of ALTER PARTITION statement failed because two partitions on different filegroups cannot be merged if either partition contains columnstore index data. Consider dropping the columnstore index before issuing the ALTER PARTITION statement, then rebuilding the columnstore index after ALTER PARTITION is complete. |
| 35346 | 16 | 0 | SPLIT clause of ALTER PARTITION statement failed because the partition is not empty. Only empty partitions can be split in when a columnstore index exists on the table. Consider an ALTER TABLE SWITCH operation from one of the nonempty partitions on the source table to a temporary staging table and then re-attempt the ALTER PARTITION SPLIT operation. Once completed, use ALTER TABLE SWITCH to move the staging table partition back to the original source table. |
| 35347 | 16 | 0 | The stored procedure 'sp_tableoption' failed because a table with a columnstore index cannot be altered to use vardecimal storage format. Consider dropping the columnstore index. |
| 35348 | 16 | 0 | The statement failed because table '%.*ls' uses vardecimal storage format. A columnstore index cannot be created on a table using vardecimal storage. Consider rebuilding the table without vardecimal storage. |
| 35349 | 16 | 0 | TRUNCATE TABLE statement failed because table '%.*ls' has a columnstore index on it. A table with a columnstore index cannot be truncated. Consider dropping the columnstore index then truncating the table. |
| 35350 | 16 | 0 | The statement failed because a columnstore index on a partitioned table must be partition-aligned with the base table. Consider dropping the columnstore index before creating a new clustered index. |
| 35351 | 16 | 0 | DROP INDEX statement failed because a columnstore index on a partitioned table must be partition-aligned with the base table (heap). Consider dropping the columnstore index before dropping a clustered index. |
| 35352 | 16 | 0 | %S_MSG statement failed because the operation cannot be performed online on a table with a columnstore index. Perform the operation without specifying the ONLINE option or drop (or disable) the columnstore index before performing the operation using the ONLINE option. |
| 35353 | 16 | 0 | %s cannot be enabled on a table with a clustered columnstore index. Consider dropping clustered columnstore index '%s' on table '%s'. |
| 35354 | 16 | 0 | The statement failed because a clustered columnstore index cannot be created on a table enabled for %S_MSG. Consider disabling %S_MSG and then creating the clustered columnstore index. |
| 35355 | 16 | 0 | The statement failed. Column '%.*ls' is either a primary key or a partitioning key that must be included, but a columnstore index cannot include a decimal or numeric data type with a precision greater than 18. Consider reducing the precision to 18. |
| 35356 | 16 | 0 | This operation is not supported on nonclustered columnstore indexes built in earlier versions of SQL Server. Consider rebuilding the index. |
| 35357 | 16 | 0 | The statement failed because a secondary dictionary reached the maximum size limit. Consider dropping the columnstore index, altering the column, then creating a new columnstore index. |
| 35358 | 16 | 0 | CREATE TRIGGER on table '%.*ls' failed because you cannot create a trigger on a table with a clustered columnstore index. Consider enforcing the logic of the trigger in some other way, or if you must use a trigger, use a heap or B-tree index instead. |
| 35359 | 16 | 0 | The statement failed because a table with a clustered columnstore index cannot have triggers. Consider removing all triggers from the table and then creating the clustered columnstore index. |
| 35360 | 16 | 0 | Referential constraint '%.*ls' cannot be created because the %S_MSG table '%.*ls' has a clustered columnstore index. |
| 35361 | 16 | 0 | The statement failed. A clustered columnstore index cannot be created over referencing column '%.*ls' on table '%.*ls'. |
| 35363 | 16 | 0 | The statement failed because clustered columnstore indexes are not supported in system databases. |
| 35364 | 16 | 0 | ALTER INDEX statement option COMPRESSION_DELAY can only be used with columnstore indexes. |
| 35365 | 22 | 0 | The compression block header at offset %ld is invalid. |
| 35366 | 22 | 0 | The columnstore blob Xpress header is invalid. |
| 35367 | 22 | 0 | The columnstore blob Xpress object header is invalid. |
| 35368 | 17 | 0 | Internal DDL Operation Error: The DDL encountered an unexpected error %d during execution (HRESULT = 0x%x). |
| 35369 | 16 | 0 | GETCHECKSUM can not be used for a table which has a clustered columnstore index. |
| 35370 | 16 | 0 | Cursors are not supported on a table which has a clustered columnstore index. |
| 35371 | 16 | 0 | SNAPSHOT isolation level is not supported on a table which has a clustered columnstore index. |
| 35372 | 16 | 0 | You cannot create more than one clustered index on %S_MSG '%.*ls'. Consider creating a new clustered index using 'with (drop_existing = on)' option. |
| 35373 | 16 | 0 | ALTER INDEX REORGANIZE statement failed on a clustered columnstore index with error %d. See previous error messages for more details. |
| 35374 | 16 | 0 | Columnstore archive decompression failed with error %d. |
| 35375 | 16 | 0 | ALTER INDEX REORGANIZE statement option COMPRESS_ALL_ROW_GROUPS can only be used with clustered columnstore indexes. |
| 35376 | 16 | 0 | Tuple mover stvf got passed invalid arguments |
| 35378 | 16 | 0 | Row groups stvf got passed invalid arguments |
| 35379 | 16 | 0 | Internal error occurred while flushing delete buffer database id %d, table id %d, index id %d, partition number %d. Additional messages in the SQL Server error log may provide more details. |
| 35380 | 16 | 0 | The non-clustered columnstore index '%.*ls' on table '%.*ls' cannot be reorganized due to an active snapshot transaction. |
| 35381 | 22 | 0 | The columnstore blob dictionary header is invalid. |
| 35382 | 16 | 0 | The specified COMPRESSION_DELAY option value %d is invalid. The valid range for disk-based table is between (0, 10080) minutes and for memory-optimized table is 0 or between (60, 10080) minutes. |
| 35383 | 16 | 0 | The use of user-defined functions is not allowed in default constraints when adding columns to a columnstore index. |
| 35384 | 16 | 0 | The statement failed because column '%.*ls' on table '%.*ls' is a lob column. Non clustered index with lob column as included column cannot co-exist with clustered columnstore index. |
| 35386 | 17 | 0 | Could not get the memory grant of %I64d KB for columnstore compression because it exceeds the maximum configuration limit of %I64d KB in the current workload group and resource pool. Please rerun query at a higher resource class, and also consider increasing DWU size. See 'https://aka.ms/sqldw_columnstore_memory' for assistance. |
| 35387 | 17 | 0 | TEMPDB ran out of space during spilling. Verify that data is evenly distributed and/or rewrite the query to consume fewer rows. If the issue still persists, consider upgrading to a higher service level objective. |
| 35388 | 15 | 0 | The statement failed because column '%.*ls' on table '%.*ls' is a persisted computed column. Adding persisted computed columns to an existing clustered columnstore index is not supported. |
| 35389 | 15 | 0 | The statement failed because column '%.*ls' on table '%.*ls' is a computed column of a LOB type. Columnstore indexes cannot include computed columns of LOB types. |
| 35390 | 16 | 0 | Computed columns in columnstore indexes are temporarily disabled. Please rewrite your query to exclude computed columns. |
| 35392 | 15 | 0 | The statement failed because column '%.*ls' on table '%.*ls' is a computed column. Nonclustered index with computed column as key or included column cannot be created on a table that has a clustered columnstore index. |
| 35401 | 10 | 0 | ONLINE |
| 35402 | 10 | 0 | ALLOW_ROW_LOCKS |
| 35403 | 10 | 0 | ALLOW_PAGE_LOCKS |
| 35404 | 16 | 0 | sequence |
| 35405 | 10 | 0 | decryption |
| 35406 | 10 | 0 | creation |
| 35409 | 10 | 0 | Replication |
| 35410 | 10 | 0 | Change Tracking |
| 35411 | 10 | 0 | Change Data Capture |
| 35412 | 16 | 0 | CloudDB Async Transport |
| 35413 | 16 | 0 | CloudDB Async Transport Forwarder |
| 35415 | 10 | 0 | mirrored |
| 35417 | 10 | 0 | primary |
| 35418 | 10 | 0 | secondary |
| 35419 | 16 | 0 | feature |
| 35420 | 16 | 0 | operation |
| 35421 | 16 | 0 | statement |
| 35422 | 16 | 0 | index option |
| 35423 | 16 | 0 | table option |
| 35424 | 16 | 0 | operator |
| 35425 | 16 | 0 | value |
| 35426 | 16 | 0 | system column |
| 35427 | 16 | 0 | set option |
| 35428 | 16 | 0 | query hint |
| 35429 | 16 | 0 | transaction isolation level |
| 35430 | 16 | 0 | in-memory index |
| 35431 | 10 | 0 | SCHEDULER |
| 35432 | 10 | 0 | NUMANODE |
| 35433 | 16 | 0 | federation |
| 35434 | 16 | 0 | federation distribution |
| 35435 | 16 | 0 | system database |
| 35436 | 16 | 0 | federation member database |
| 35437 | 16 | 0 | non federation member database |
| 35438 | 16 | 0 | federation root database |
| 35439 | 10 | 0 | it is a system database. |
| 35440 | 10 | 0 | it acts as a distribution database |
| 35441 | 10 | 0 | an internal error occurred |
| 35442 | 10 | 0 | it is involved in a mirroring session. Turn off the mirroring session and try again |
| 35443 | 10 | 0 | it is not in SIMPLE recovery mode. Change the recovery model to SIMPLE and try again |
| 35444 | 10 | 0 | it is a database snapshot |
| 35445 | 10 | 0 | it is a not currently enabled |
| 35446 | 16 | 0 | clause |
| 35447 | 10 | 0 | Cluster Proxy |
| 35448 | 10 | 0 | partition |
| 35449 | 16 | 0 | signing algorithm |
| 35450 | 16 | 0 | table |
| 35451 | 16 | 0 | join hint |
| 35452 | 10 | 0 | Database unavailable |
| 35453 | 10 | 0 | it is a system database. Make sure to target a user database. If you want temporary clustered columnstore tables, consider creating a regular user database for them |
| 35454 | 10 | 0 | a transaction is currently active. Execute sp_db_enable_clustered_columnstores by itself |
| 35455 | 10 | 0 | an internal error occurred |
| 35456 | 10 | 0 | it is involved in a mirroring pair. Consider disabling mirroring, changing the setting, then re-establishing mirroring |
| 35457 | 10 | 0 | it is a database snapshot |
| 35458 | 10 | 0 | it is part of an Always On availability group. Consider removing the database from the availability group, changing the setting, and then adding the database back to the availability group |
| 35459 | 10 | 0 | it is a replication distribution database. Make sure to target a regular user database |
| 35460 | 10 | 0 | it is not using the SIMPLE recovery model. Consider temporarily changing to the simple recovery model, then downgrading, then switching back |
| 35461 | 10 | 0 | it contains one or more clustered columnstore indexes. Consider dropping these indexes or creating clustered B-tree indexes instead, and trying again |
| 35462 | 10 | 0 | referencing |
| 35463 | 10 | 0 | referenced |
| 35464 | 10 | 0 | columnstore indexes are not supported in the current SQL Server edition. See SQL Server Books Online for supported editions |
| 35465 | 17 | 0 | Unable to allocate the recovery thread |
| 35466 | 16 | 0 | Exception in the recovery thread |
| 35467 | 16 | 0 | Already linked to a partition host |
| 35468 | 16 | 0 | Partition DB marked as suspect |
| 35469 | 16 | 0 | Failed to get Partition DB attributes |
| 35470 | 16 | 0 | Partition Host |
| 35471 | 10 | 0 | Partition metadata not found |
| 35472 | 15 | 0 | memory optimized tables |
| 35473 | 15 | 0 | natively compiled modules |
| 35474 | 15 | 0 | indexes on memory optimized tables |
| 35475 | 15 | 0 | hash indexes |
| 35476 | 15 | 0 | transactions that access memory optimized tables or natively compiled modules |
| 35477 | 15 | 0 | databases that have a MEMORY_OPTIMIZED_DATA filegroup |
| 35478 | 16 | 0 | truncate |
| 35479 | 16 | 0 | start |
| 35480 | 16 | 0 | stop |
| 35481 | 15 | 0 | memory optimized table types |
| 35482 | 16 | 0 | clustered |
| 35483 | 16 | 0 | nonclustered |
| 35484 | 16 | 0 | BUCKET_COUNT |
| 35485 | 16 | 0 | security policy |
| 35486 | 15 | 0 | memory optimized tables that have a column store index |
| 35487 | 10 | 0 | Global Transactions |
| 35488 | 15 | 0 | natively compiled triggers |
| 35489 | 16 | 0 | Upgrade of Hekaton database |
| 35490 | 16 | 0 | memory optimized tables that have max length columns |
| 35491 | 16 | 0 | max length columns in natively compiled modules |
| 35492 | 16 | 0 | column definition |
| 35493 | 16 | 0 | enabled |
| 35494 | 16 | 0 | disabled |
| 35495 | 15 | 0 | memory optimized table |
| 35496 | 15 | 0 | natively compiled module |
| 35497 | 15 | 0 | module |
| 35498 | 16 | 0 | external data source |
| 35499 | 16 | 0 | OUTPUT clauses in natively compiled modules |
| 35501 | 15 | 0 | schemas that contain natively compiled modules |
| 35502 | 15 | 0 | change_tracking_hardened_cleanup_version() |
| 35503 | 15 | 0 | safe_cleanup_version() |
| 35504 | 16 | 0 | server encryption protector |
| 35505 | 15 | 0 | RESUMABLE |
| 35506 | 15 | 0 | MAX_DURATION |
| 35507 | 10 | 0 | Storage |
| 35508 | 10 | 0 | RESUME |
| 35509 | 10 | 0 | PAUSE |
| 35510 | 10 | 0 | ABORT |