Tag: SQL Server Errors

SQL Server Error Msg 9047 – Async recovery thread has exited unexpectedly, shutting down xlog reader.

SQL Server Error Msg 16 – 13557

SQL Server Error Msg 10026 – No command text was set.

SQL Server Error Msg Cannot create a worktable row larger than allowable maximum. Resubmit your query with the ROBUST PLAN hint. – 16

SQL Server Error Msg 4071 – The XP callback function ‘%.*ls’ failed in extended procedure ‘%.*ls’ because it was executed within an INSERT-EXEC statement which does not allow the extended procedure to send information other than result set.

SQL Server Error Msg 49806 – DynamicActivation feature switch is not enabled for all remote storage DB: Server ‘%.*ls’, Database ‘%.*ls’, ServiceLevelObjective ‘%.*ls’

SQL Server Error Msg 20810 – The specified source object must be a user-defined aggregate object if it is published as an ‘aggregate schema only’ type article.

SQL Server Error Msg 16 – 13575

SQL Server Error Msg 25017 – Failed to execute the command “%s” through xp_cmdshell. Detailed error information is returned in a result set.

SQL Server Error Msg 33053 – Extensible Key Management is disabled or not supported on this edition of SQL Server.  Use sp_configure ‘EKM provider enabled’ to enable it.

SQL Server Error Msg 35415 – mirrored

SQL Server Error Msg 33027 – Cannot load library ‘%.*ls’. See errorlog for more information.

SQL Server Error Msg 2597 – Ignoring trace flag %d. It is either an invalid trace flag or a trace flag that can only be specified during server startup.

SQL Server Error Msg 40074 – Partition key is not found is the target rowset or is nullable or not part of index keys.

SQL Server Error Msg 6978 – Invalid item type for list type ‘%s’. The item type of a list may not itself be a list, and types derived from ID may not be used as item types in this release.

SQL Server Error Msg 5029 – Warning: The log for database ‘%.*ls’ has been rebuilt. Transactional consistency has been lost. The RESTORE chain was broken, and the server no longer has context on the previous log files, so you will need to know what they were. You should run DBCC CHECKDB to validate physical consistency. The database has been put in dbo-only mode. When you are ready to make the database available for use, you will need to reset database options and delete any extra log files.

SQL Server Error Msg 2394 – %sThere is no function ‘%ls()’

SQL Server Error Msg predicate source – 10

SQL Server Error Msg 9104 – auto statistics internal

SQL Server Error Msg 15357 – The current security context was set by “%ls”. It cannot be reverted by statement “%ls”.