SQL Server

SQL Server Error Msg 35312 – 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.

SQL Server Error Msg 15149 – Principal doesn’t exist or doesn’t have sufficient privileges.

SQL Server Error Msg 35002 – Server type and parent Server Group type are not the same

SQL Server Error Msg 21861 – The current operation was aborted because it would deactivate an article in a publication for which a snapshot was being generated.

SQL Server Error Msg 14228 – Server MSX enlistment changed from ‘%s’ to ‘%s’.

SQL Server Error Msg 3963 – Transaction failed in database ‘%.*ls’ because distributed transactions are not supported under snapshot isolation.

SQL Server Error Msg 21611 – Cannot drop the distribution Publisher “%s” because it has publications defined. Drop the publications first.

SQL Server Error Msg 4625 – There is no such server principal %.*s or you do not have permission.

SQL Server Error Msg 46906 – Unable to retrieve registry value ‘%ls’ from Windows registry key ‘%ls’: %ls.

SQL Server Error Msg 21356 – Warning: only Subscribers running SQL Server 7.0 Service Pack 2 or later can synchronize with publication ‘%s’ because publication wide validation task is performed.

SQL Server Error Msg Cannot insert explicit value for identity column in table ‘%.*ls’ when IDENTITY_INSERT is set to OFF. – 16

SQL Server Error Msg 4902 – Cannot find the object “%.*ls” because it does not exist or you do not have permissions.

SQL Server Error Msg 33405 – An error occurred during the %S_MSG %S_MSG operation on a FileTable object. (HRESULT = ‘0x%08x’).

SQL Server Error Msg 28608 – Federated transaction could not be started at this time because the TCM Agent is not in a state, which allows new transactions to begin. The TCM Agent is currently in state: %d. The most common reason for this is that the system is being shutdown. Previous messages in the log should contain additional information.

SQL Server Error Msg 9233 – The option ‘Service’ must be specified in the notification options identifier.

SQL Server Error Msg 40193 – The maximum allowed number of database is already paired.

SQL Server Error Msg 17894 – Dispatcher (0x%lx) from dispatcher pool ‘%.*ls’ Worker 0x%p appears to be stuck on Node %ld. Approx CPU Used: kernel %I64d ms, user %I64d ms, Interval: %I64d.

SQL Server Error Msg 35351 – 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.

SQL Server Error Msg 32048 – Database Mirroring Monitor Schedule

SQL Server Error Msg 27018 – Could not retrieve metadata from Error Tolerant Index.  The index is probably corrupt.