SQL Server

SQL Server Error Msg 16200 – The statement failed because ‘APPROX_COUNT_DISTINCT’ does not support DISTINCT parameters. Consider using ‘APPROX_COUNT_DISTINCT’ without DISTINCT, or COUNT or COUNT_BIG with DISTINCT.

SQL Server Error Msg 17676 – SQL Server shutdown due to Ctrl-C or Ctrl-Break signal. This is an informational message only. No user action is required.

SQL Server Error Msg 30036 – Search property list ‘%.*ls’ cannot be dropped because it is being used by at least one full-text index. To identify the full-text indexes that are using the search property list, obtain the search property list id from the property_list_id column of the sys.registered_search_property_lists catalog view, and then obtain the object ID of every table or indexed view whose full-text index is associated with this search property list from the object_id and property_list_id columns of the sys.fulltext_indexes catalog view . For each full-text index, either remove the search property list or drop the full-text index, if it is no longer needed. To remove the search property list, use ALTER FULLTEXT INDEX ON SET SEARCH PROPERTY LIST OFF;. To drop a full-text index, use DROP FULLTEXT INDEX ON ;.

SQL Server Error Msg 9454 – XML parsing: line %d, character %d, no ‘]]>’ in element content

SQL Server Error Msg 45155 – A free database operation is already in progress for subscription ‘%ld’. Subscription can have only one free database per region. To provision another free database in same subscription, choose a different region. To provision another free database in same region, use different subscription.

SQL Server Error Msg 21034 – Rows inserted or updated at the Subscriber cannot be outside the article partition.

SQL Server Error Msg 33254 – This operation cannot be performed in the master database.

SQL Server Error Msg 28066 – A corrupted message has been received. The security dialog message header is invalid. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.

SQL Server Error Msg 41636 – Fabric Service ‘%ls’ (partition ID ‘%ls’) is unable to enqueue a work item for the database restart of ‘%ls’ database (ID %d). The administrator may have exhausted all available resources.  If this condition persists, contact the system administrator.

SQL Server Error Msg 35492 – column definition

SQL Server Error Msg 8947 – Table error: Multiple IAM pages for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) contain allocations for the same interval. IAM pages %S_PGID and %S_PGID.

SQL Server Error Msg 18361 – Reason: Could not find a user matching the name provided. [Database: ‘%.*ls’]

SQL Server Error Msg History table ‘%.*ls’ can not be memory optimized table. – 16

SQL Server Error Msg 41659 – Checkpoint for Database ‘%ls’ (ID %d) failed. Encountered error (error code: 0x%08X).

SQL Server Error Msg 11275 – A corrupted message has been received. The End of Conversation and Error flags are both set. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.

SQL Server Error Msg 47043 – Reason: Token-based server access validation failed with an infrastructure error. Login is disabled.

SQL Server Error Msg 11240 – A corrupted message has been received. The binary message preamble is malformed.

SQL Server Error Msg 10058 – The consumer cannot insert a new row before releasing previously-retrieved row handles.

SQL Server Error Msg 40590 – The Gpm is in rebuild and cannot be accessed as it is not yet consistent.

SQL Server Error Msg 111 – ‘CREATE FUNCTION’ must be the first statement in a query batch