SQL Server

SQL Server Error Msg 22834 – Could not modify the the verbose logging status for table %s. The failure occurred when executing the command ‘%s’. The error returned was %d: ‘%s’. Use the action and error to determine the cause of the failure and resubmit the request.

SQL Server Error Msg 5095 – A database or filegroup cannot be set to read-only mode when any files are subject to a RESTORE PAGE operation. Complete the restore sequence involving file “%ls” before attempting to transition to read-only.

SQL Server Error Msg 28074 – Service Broker could not upgrade conversation with conversation_handle ‘%ls’. Use END CONVERSATION … WITH CLEANUP to delete this conversation, then try again to enable the broker. Use ALTER DATABASE … SET ERROR_BROKER to error all conversations in this database. Use ALTER DATABASE … SET NEW_BROKER to delete all conversations in this database.

SQL Server Error Msg 18784 – The alternate snapshot folder path generated by replication has been truncated. Reconfigure the publication to use a shorter alternate snapshot folder path, and then retry the operation.

SQL Server Error Msg 30022 – Warning: The configuration of a full-text stoplist was modified using the WITH NO POPULATION clause. This put the full-text index into an inconsistent state. To bring the full-text index into a consistent state, start a full population. The basic Transact-SQL syntax for this is: ALTER FULLTEXT INDEX ON table_name START FULL POPULATION.

SQL Server Error Msg 7812 – The endpoint ‘%.*ls’ has been established in metadata, but HTTP listening has not been enabled because HTTP support did not start successfully. Verify that the operating system and the edition of SQL Server supports native HTTP access. Check the SQL Server error log for any errors that might have occurred while starting HTTP support.

SQL Server Error Msg Cannot create a row of size %d which is greater than the allowable maximum row size of %d. – 16

SQL Server Error Msg 20694 – One or more rows to be updated for table %s contain changes in the column %s, which is used in one or more filters; merge replication cannot use batch processing for these changes. No action is required, but if this condition occurs frequently, verify that data is partitioned optimally. Batch updates can improve the performance of merge replication.

SQL Server Error Msg 16646 – The sync member is already being dropped.

SQL Server Error Msg 33297 – Cannot create %S_MSG. The %S_MSG cannot be empty.

SQL Server Error Msg 10321 – Method name ‘%.*ls’ is invalid for UserDefinedType method call.

SQL Server Error Msg 4868 – The bulk load failed. The codepage “%d” is not installed. Install the codepage and run the command again.

SQL Server Error Msg 477 – Invalid ROWS value or REPEATABLE seed in the TABLESAMPLE clause for table “%.*ls”. The value or seed must be an integer.

SQL Server Error Msg 5206 – %.*ls: Page %d:%d could not be moved because it could not be read.

SQL Server Error Msg 46643 – external tables

SQL Server Error Msg 2749 – Identity column ‘%.*ls’ must be of data type int, bigint, smallint, tinyint, or decimal or numeric with a scale of 0, unencrypted, and constrained to be nonnullable.

SQL Server Error Msg 33278 – Cannot assign the same encryption scheme to two expressions at line ‘%d’. The encryption scheme of the first expression is %ls and the encryption scheme of the second expression is %ls. Other columns/variables with the same encryption scheme as the first expression are: %.*ls. Other columns/variables with the same encryption scheme as the second expression are: %.*ls.

SQL Server Error Msg 14270 – Job ‘%s’ is not currently targeted at server ‘%s’.

SQL Server Error Msg 40042 – Corrupted column length.

SQL Server Error Msg 10961 – The request has been aborted because its CPU usage exceeds the maximum configured limit for the workload group.