In this blog post, you’ll learn more about the SQL Server Error Code 40051 and the error message description that is shown SQL Server Error Code 40051 SQL Server Error Description for the Code :40051 Use of UPDATETEXT on replicated tables is not supported.

In this blog post, you’ll learn more about the SQL Server Error Code 41904 and the error message description that is shown SQL Server Error Code 41904 SQL Server Error Description for the Code :41904 BACKUP DATABASE failed. SQL Database Managed Instance supports only COPY_ONLY full database backups which are initiated by user.

In this blog post, you’ll learn more about the SQL Server Error Code 5105 and the error message description that is shown SQL Server Error Code 5105 SQL Server Error Description for the Code :5105 A file activation error occurred. The physical file name ‘%.*ls’ may be incorrect. Diagnose and correct additional errors, and retry the operation.

In this blog post, you’ll learn more about the SQL Server Error Code 6322 and the error message description that is shown SQL Server Error Code 6322 SQL Server Error Description for the Code :6322 XML Parser ran out of memory. This could be caused by too many attributes or namespace declarations.

In this blog post, you’ll learn more about the SQL Server Error Code 7312 and the error message description that is shown SQL Server Error Code 7312 SQL Server Error Description for the Code :7312 Invalid use of schema or catalog for OLE DB provider “%ls” for linked server “%ls”. A four-part name was supplied, but the provider does not expose the necessary interfaces to…

In this blog post, you’ll learn more about the SQL Server Error Code 15654 and the error message description that is shown SQL Server Error Code 15654 SQL Server Error Description for the Code :15654 Table %s: cannot perform the operation on the table because its clustered index is disabled.

In this blog post, you’ll learn more about the SQL Server Error Code 11440 and the error message description that is shown SQL Server Error Code 11440 SQL Server Error Description for the Code :11440 The ALTER TABLE SWITCH statement failed because table ‘%.*ls’ has ordered clustered columnstore index ‘%.*ls’ and table ‘%.*ls’ does not.

In this blog post, you’ll learn more about the SQL Server Error Code 12427 and the error message description that is shown SQL Server Error Code 12427 SQL Server Error Description for the Code :12427 Cannot perform operation on Query Store while it is enabled. Please turn off Query Store for the database and try again.

In this blog post, you’ll learn more about the SQL Server Error Code 4336 and the error message description that is shown SQL Server Error Code 4336 SQL Server Error Description for the Code :4336 The filegroup “%ls” has been dropped and cannot be restored into the online database.

In this blog post, you’ll learn more about the SQL Server Error Code 16011 and the error message description that is shown SQL Server Error Code 16011 SQL Server Error Description for the Code :16011 The data masking function for column ‘%.*ls’ is too long.

In this blog post, you’ll learn more about the SQL Server Error Code 151 and the error message description that is shown SQL Server Error Code 151 SQL Server Error Description for the Code :151 ?%.*ls? is an invalid money value.

In this blog post, you’ll learn more about the SQL Server Error Code 8386 and the error message description that is shown SQL Server Error Code 8386 SQL Server Error Description for the Code :8386 Use of hint “%.*ls” on the target table of INSERT is deprecated because it may be removed in a future version of SQL Server. Modify the INSERT statement to remove…

In this blog post, you’ll learn more about the SQL Server Error Code 20717 and the error message description that is shown SQL Server Error Code 20717 SQL Server Error Description for the Code :20717 sp_addmergelogsettings failed to add log settings. If log settings already exist for this subscription then use sp_changemergelogsettings to change the settings or sp_dropmergelogsettings to remove the settings.

In this blog post, you’ll learn more about the SQL Server Error Code 21597 and the error message description that is shown SQL Server Error Code 21597 SQL Server Error Description for the Code :21597 The article includes only the rowguidcol column. You must publish at least one other column.

In this blog post, you’ll learn more about the SQL Server Error Code 22554 and the error message description that is shown SQL Server Error Code 22554 SQL Server Error Description for the Code :22554 Cannot change publication “%s” to use the sync_mode of “character” because it uses a retention period unit other than “day”. Use sp_changemergepublication to set the retention period unit to “day”.

In this blog post, you’ll learn more about the SQL Server Error Code 1719 and the error message description that is shown SQL Server Error Code 1719 SQL Server Error Description for the Code :1719 FILESTREAM data cannot be placed on an empty filegroup.

In this blog post, you’ll learn more about the SQL Server Error Code 5127 and the error message description that is shown SQL Server Error Code 5127 SQL Server Error Description for the Code :5127 All files must be specified for database snapshot creation. Missing the file “%ls”.

In this blog post, you’ll learn more about the SQL Server Error Code 13077 and the error message description that is shown SQL Server Error Code 13077 SQL Server Error Description for the Code :13077 a cursor declaration

In this blog post, you’ll learn more about the SQL Server Error Code 35314 and the error message description that is shown SQL Server Error Code 35314 SQL Server Error Description for the Code :35314 The statement failed because a columnstore index cannot be created on a column set. Consider creating a nonclustered columnstore index on a subset of columns in the table that does…

In this blog post, you’ll learn more about the SQL Server Error Code 47036 and the error message description that is shown SQL Server Error Code 47036 SQL Server Error Description for the Code :47036 Reason: Login failed because USE db failed while checking firewall rules.