In this blog post, you’ll learn more about the SQL Server Error Code 49902 and the error message description that is shown SQL Server Error Code 49902 SQL Server Error Description for the Code :49902 There are not enough worker threads available for the number of CPUs. This is because one or more CPUs were added. To increase the number of worker threads, use sp_configure…

In this blog post, you’ll learn more about the SQL Server Error Code 45126 and the error message description that is shown SQL Server Error Code 45126 SQL Server Error Description for the Code :45126 Parameter “%ls” is invalid.

In this blog post, you’ll learn more about the SQL Server Error Code 1051 and the error message description that is shown SQL Server Error Code 1051 SQL Server Error Description for the Code :1051 Cursor parameters in a stored procedure must be declared with OUTPUT and VARYING options, and they must be specified in the order CURSOR VARYING OUTPUT.

In this blog post, you’ll learn more about the SQL Server Error Code 1797 and the error message description that is shown SQL Server Error Code 1797 SQL Server Error Description for the Code :1797 Sparse column ?%.*ls? cannot be used to federate the table ?%.*ls?.

In this blog post, you’ll learn more about the SQL Server Error Code 14601 and the error message description that is shown SQL Server Error Code 14601 SQL Server Error Description for the Code :14601 Operator “%s” is not enabled and therefore cannot receive notifications.

In this blog post, you’ll learn more about the SQL Server Error Code 16652 and the error message description that is shown SQL Server Error Code 16652 SQL Server Error Description for the Code :16652 Cannot update the sync group because it is currently being dropped.

In this blog post, you’ll learn more about the SQL Server Error Code 4154 and the error message description that is shown SQL Server Error Code 4154 SQL Server Error Description for the Code :4154 UNNEST can only take an expression of type multiset.

In this blog post, you’ll learn more about the SQL Server Error Code 8642 and the error message description that is shown SQL Server Error Code 8642 SQL Server Error Description for the Code :8642 The query processor could not start the necessary thread resources for parallel query execution. Reduce load on the server or use the MAXDOP setting to limit parallelism.

In this blog post, you’ll learn more about the SQL Server Error Code 14631 and the error message description that is shown SQL Server Error Code 14631 SQL Server Error Description for the Code :14631 The current user (‘%s’) either does not have permission to access the database specified in the parameter @execute_query_database or cannot impersonate the user specified in the parameter @execute_query_as. Only members…

In this blog post, you’ll learn more about the SQL Server Error Code 41146 and the error message description that is shown SQL Server Error Code 41146 SQL Server Error Description for the Code :41146 Failed to bring Availability Group ‘%.*ls’ online.  If this is a WSFC availability group, the Windows Server Failover Clustering (WSFC) service may not be running, or it may not be…

In this blog post, you’ll learn more about the SQL Server Error Code 21221 and the error message description that is shown SQL Server Error Code 21221 SQL Server Error Description for the Code :21221 The specified source object must be a view object if it is going to be as a ‘view schema only’ type article.

In this blog post, you’ll learn more about the SQL Server Error Code 43033 and the error message description that is shown SQL Server Error Code 43033 SQL Server Error Description for the Code :43033 The primary server %.*ls already has the maximum of replica servers.

In this blog post, you’ll learn more about the SQL Server Error Code 27145 and the error message description that is shown SQL Server Error Code 27145 SQL Server Error Description for the Code :27145 ‘%ls’ is not a valid project name. It consists of characters that are not allowed.

In this blog post, you’ll learn more about the SQL Server Error Code 33313 and the error message description that is shown SQL Server Error Code 33313 SQL Server Error Description for the Code :33313 An out of memory condition has occurred in the Service Broker transport layer. A service broker connection is closed due to this condition.

In this blog post, you’ll learn more about the SQL Server Error Code 45427 and the error message description that is shown SQL Server Error Code 45427 SQL Server Error Description for the Code :45427 Hardware generation of the source is ‘%.*ls’ while that of the PITR target is ‘%.*ls’.

In this blog post, you’ll learn more about the SQL Server Error Code 17109 and the error message description that is shown SQL Server Error Code 17109 SQL Server Error Description for the Code :17109 FallBack certificate was successfully created.

In this blog post, you’ll learn more about the SQL Server Error Code 3953 and the error message description that is shown SQL Server Error Code 3953 SQL Server Error Description for the Code :3953 Snapshot isolation transaction failed in database ?%.*ls? because the database was not recovered when the current transaction was started. Retry the transaction after the database has recovered.

In this blog post, you’ll learn more about the SQL Server Error Code 18768 and the error message description that is shown SQL Server Error Code 18768 SQL Server Error Description for the Code :18768 The specified LSN {%08lx:%08lx:%04lx} for repldone log scan occurs before the current start of replication in the log {%08lx:%08lx:%04lx}.

In this blog post, you’ll learn more about the SQL Server Error Code 27016 and the error message description that is shown SQL Server Error Code 27016 SQL Server Error Description for the Code :27016 Cannot connect to Error Tolerant Index.  Bad or missing SqlCommand object.

In this blog post, you’ll learn more about the SQL Server Error Code 49512 and the error message description that is shown SQL Server Error Code 49512 SQL Server Error Description for the Code :49512 Session level trace flags are not supported on managed instance.