SQL Server

SQL Server Error Msg 6232 – Type “%.*ls.%.*ls” is marked for native serialization, but base type “%.*ls.%.*ls” is not marked with “LayoutKind.Sequential”. Native serialization requires the type to be marked with “LayoutKind.Sequential”.

SQL Server Error Msg 49820 – Managed Server Resource Stats Timer task encountered an error (SQL Error Code: %d).

SQL Server Error Msg System-versioned table cannot have more than one SYSTEM_TIME period definition. – 16

SQL Server Error Msg 4077 – The statement failed because the sql_variant value uses collation %.*ls, which is not recognized by older client drivers. Try upgrading the client operating system or applying a service update to the database client software, or use a different collation. See SQL Server Books Online for more information on changing collations.

SQL Server Error Msg 5340 – WITH schema clause cannot be specified together with FORMATFILE or SINGLE_BLOB/SINGLE_CLOB/SINGLE_NCLOB option.

SQL Server Error Msg 10115 – Cannot create %S_MSG on view “%.*ls” because it uses the UNPIVOT operator. Consider not indexing this view.

SQL Server Error Msg 6975 – Invalid redefinition of attribute ‘%s’ in type ‘%s’. Must be fixed to the same value as in the derived type.

SQL Server Error Msg 4860 – Cannot bulk load. The file “%ls” does not exist or you don’t have file access rights.

SQL Server Error Msg 9950 – Informational: Full-text catalog health monitor reported a failure for catalog ‘%ls’ (‘%d’) in database ‘%ls’ (‘%d’). Reason code: %d. Error: %ls. The catalog is corrupted and all in-progress populations will be stopped. Use rebuild catalog to recover the failure and start population from scratch.

SQL Server Error Msg 14844 – Remote database ‘%.*ls’ has completed copying, and is now online.

SQL Server Error Msg 11294 – This forwarded message has been dropped because the destination route is not valid.

SQL Server Error Msg 19236 – Negotiated security context is missing an integrity flag.

SQL Server Error Msg 3188 – The backup set was written with damaged data by a BACKUP WITH CONTINUE_AFTER_ERROR.

SQL Server Error Msg 7311 – Cannot obtain the schema rowset “%ls” for OLE DB provider “%ls” for linked server “%ls”. The provider supports the interface, but returns a failure code when it is used.

SQL Server Error Msg 4154 – UNNEST can only take an expression of type multiset.

SQL Server Error Msg 6281 – ALTER ASSEMBLY failed because only users with ALTER ANY SCHEMA permissions can use WITH UNCHECKED DATA.

SQL Server Error Msg 7934 – DBCC CHECK cannot proceed on database %.*ls because it is a Secondary Replica and either Snapshot creation failed or the WITH TABLOCK option was specified. Secondary Replica databases cannot be exclusively locked for DBCC CHECK. Reason may have been given in previous error.

SQL Server Error Msg 11032 – The table was in immediate-update mode, and deleting a single row caused more than one row to be deleted in the data source.

SQL Server Error Msg 10707 – The CUBE() and ROLLUP() grouping constructs are not allowed in the current compatibility mode.  They are only allowed in 100 mode or higher.

SQL Server Error Msg 10325 – The server is shutting down due to stack overflow in user’s unmanaged code.