In this blog post, you’ll learn more about the SQL Server Error Code 36005 and the error message description that is shown SQL Server Error Code 36005 SQL Server Error Description for the Code :36005 Dac root – database %s does not exist.

In this blog post, you’ll learn more about the SQL Server Error Code 46903 and the error message description that is shown SQL Server Error Code 46903 SQL Server Error Description for the Code :46903 This stored procedure is not available because Polybase feature is not enabled.

In this blog post, you’ll learn more about the SQL Server Error Code 4165 and the error message description that is shown SQL Server Error Code 4165 SQL Server Error Description for the Code :4165 The score override argument, if present in one of the subqueries, must be present in all subqueries and must be the same constant and variable.

In this blog post, you’ll learn more about the SQL Server Error Code 492 and the error message description that is shown SQL Server Error Code 492 SQL Server Error Description for the Code :492 Duplicate column names are not allowed in result sets obtained through OPENQUERY and OPENROWSET. The column name ?%.*ls? is a duplicate.

In this blog post, you’ll learn more about the SQL Server Error Code 7642 and the error message description that is shown SQL Server Error Code 7642 SQL Server Error Description for the Code :7642 A full-text catalog named ‘%ls’ already exists in this database. Use a different name.

In this blog post, you’ll learn more about the SQL Server Error Code 30080 and the error message description that is shown SQL Server Error Code 30080 SQL Server Error Description for the Code :30080 The full-text population on table ‘%ls’ cannot be started because the full-text catalog is importing data from existing catalogs. After the import operation finishes, rerun the command.

In this blog post, you’ll learn more about the SQL Server Error Code 35288 and the error message description that is shown SQL Server Error Code 35288 SQL Server Error Description for the Code :35288 Always On Availability Groups log apply for availability database “%.*ls” has received an out-of-order log block.  The expected LSN was %S_LSN.  The received LSN was %S_LSN.  The database replica has…

In this blog post, you’ll learn more about the SQL Server Error Code 41188 and the error message description that is shown SQL Server Error Code 41188 SQL Server Error Description for the Code :41188 Availability group ‘%.*ls’ failed to process %s-%s command.  The operation encountered SQL Server error %d before the availability group configuration could be updated, and has been rolled back.  Refer to…

In this blog post, you’ll learn more about the SQL Server Error Code 41603 and the error message description that is shown SQL Server Error Code 41603 SQL Server Error Description for the Code :41603 The transport subscriber failed to process the build secondary replica event (partition ID %ls).  If this condition persists, contact the system administrator.

In this blog post, you’ll learn more about the SQL Server Error Code 41851 and the error message description that is shown SQL Server Error Code 41851 SQL Server Error Description for the Code :41851 Memory optimized segment table consistency error detected. Segment definition ordering does not match the (strict) logical ordering. Older Segment CkptId = %I64d, LsnInfo = (%I64d:%hu), TxBegin = %I64d, TxEnd =…

In this blog post, you’ll learn more about the SQL Server Error Code 1505 and the error message description that is shown SQL Server Error Code 1505 SQL Server Error Description for the Code :1505 The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name ?%.*ls? and the index name ?%.*ls?. The duplicate key value is %ls.

In this blog post, you’ll learn more about the SQL Server Error Code 7896 and the error message description that is shown SQL Server Error Code 7896 SQL Server Error Description for the Code :7896 The column or parameter ‘%.*ls’ uses a data type not supported by SOAP.  SOAP only supports data types supported in SQL Server 2005 or earlier.