Tag: SQL Server Errors

SQL Server Error Msg 13708 – System-versioned table schema modification failed because history table ‘%.*ls’ has triggers defined. Consider dropping all triggers and trying again.

SQL Server Error Msg 14002 – Could not find the ‘Sync’ subsystem with the task ID %ld.

SQL Server Error Msg 46613 – DATE_FORMAT

SQL Server Error Msg 21171 – Could not find package ‘%s’ in msdb at server ‘%s’.

SQL Server Error Msg 30120 – Invalid brick GUID.

SQL Server Error Msg 41917 – Dropping local instance via sp_dropserver is not allowed in SQL Database Managed Instance.

SQL Server Error Msg 45415 – Creating secondary of secondary (a process known as chaining) is not supported when enabling Transparent Data Encryption using Azure Key Vault (BYOK).

SQL Server Error Msg 7375 – Cannot open index “%ls” on table “%ls” from OLE DB provider “%ls” for linked server “%ls”. %ls

SQL Server Error Msg 15328 – The database is offline already.

SQL Server Error Msg 7925 – Index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). %I64d pages used in %I64d dedicated extents.

SQL Server Error Msg 2513 – DBCC DBREINDEX cannot be used on memory optimized tables.

SQL Server Error Msg 6544 – %s ASSEMBLY for assembly ‘%.*ls’ failed because assembly ‘%.*ls’ is malformed or not a pure .NET assembly. %.*ls

SQL Server Error Msg 33430 – Killed %d non-transactional FILESTREAM handles from database ID %d.

SQL Server Error Msg 8316 – Cannot open registry key ‘HKLM\%ls’. SQL Server performance counters are disabled.

SQL Server Error Msg 20061 – The compatibility level of this database must be set to 70 or higher to be enabled for merge publishing.

SQL Server Error Msg 14287 – The ‘%s’ supplied has an invalid %s.

SQL Server Error Msg 21050 – Only members of the sysadmin fixed server role or db_owner fixed database role can perform this operation. Contact an administrator with sufficient permissions to perform this operation.

SQL Server Error Msg 45352 – Create Managed Instance failed. Provided virtual network subnet is located in %ls, which is a different region than the one you are provisioning Managed Instance in (%ls). To create a VNET-joined Managed Instance, the instance and the virtual network have to be located in the same region.

SQL Server Error Msg 7942 – DBCC %ls scanning ‘%.*ls’ table…

SQL Server Error Msg 21157 – The snapshot compression option can be enabled only for a publication having an alternate snapshot generation folder defined.