SQL Server

SQL Server Error Msg 1462 – Database mirroring is disabled due to a failed redo operation. Unable to resume.

SQL Server Error Msg 13704 – System-versioned table schema modification failed because history table ‘%.*ls’ has IDENTITY column specification. Consider dropping all IDENTITY column specifications and trying again.

SQL Server Error Msg 41397 – The TOP operator can return a maximum of %d sorted rows. %d was requested. Reduce the number of rows selected or simplify the query.

SQL Server Error Msg 16 – 13585

SQL Server Error Msg 33426 – INSERT, UPDATE, DELETE, or MERGE to FileTable ‘%.*ls’ is not allowed inside a trigger on a FileTable.

SQL Server Error Msg 3938 – The transaction has been stopped because it conflicted with the execution of a FILESTREAM close operation using the same transaction.  The transaction will be rolled back.

SQL Server Error Msg 11602 – %ls statements are not verified.

SQL Server Error Msg 8192 – Replication filter procedures cannot have parameters.

SQL Server Error Msg 7312 – Invalid use of schema or catalog for OLE DB provider “%ls” for linked server “%ls”. A four-part name was supplied, but the provider does not expose the necessary interfaces to use a catalog or schema.

SQL Server Error Msg 9947 – Warning: Identity of full-text catalog in directory ‘%ls’ does not match database ‘%.*ls’. The full-text catalog cannot be attached.

SQL Server Error Msg 15124 – The configuration option ‘%s’ is not unique.

SQL Server Error Msg 7608 – An unknown full-text failure (0x%x) occurred during “%hs”.

SQL Server Error Msg 8422 – The error description is missing. Specify a description of the error.

SQL Server Error Msg 35483 – nonclustered

SQL Server Error Msg 5527 – The primary FILESTREAM log file cannot be dropped because other FILESTREAM filegroups exist.

SQL Server Error Msg 10335 – The Common Language Runtime (CLR) was loaded in an unsupported manner. This can occur if an extended stored procedure or OLE Automation object running in SQL Server calls into managed code before the CLR integration runtime host loads the CLR. You need to restart SQL Server to use CLR integration features.

SQL Server Error Msg 20705 – Cannot set @conflict_logging to ‘both’ because publication ‘%s’ has a compatibility level lower than 90. Set @publication_compatibility_level to ’90RTM’ when creating the publication or use sp_changemergepublication to set publication_compatibility_level to ’90RTM’.

SQL Server Error Msg 33111 – Cannot find server %S_MSG with thumbprint ‘%.*ls’.

SQL Server Error Msg 21550 – Before you drop the column from the publication, all computed columns that depend on column ‘%s’ must be dropped.

SQL Server Error Msg 45369 – No baseline is set for rule ID: %d. You should first set a baseline for this rule.