TOP KNOWN ISSUES WITH MICROSOFT SQL SERVER 2014 CU4

SQLServerF1

You may receive below error on a table that contains non-unique indexes and when you run a query to update the table by using the bitmap index that contains a partition key
Msg 2601, Level 14, State 1, Line 1
Cannot insert duplicate key row in object <table name> with unique index <index name>. The duplicate key value is (0, <the value>).
The issue has been fixed in the cumulative update 4 (CU4) of SQL Server 2014.
https://support.microsoft.com/kb/2999197

You may receive below kind of deadlock error when parallelism is used at server or query level.
(Process ID 85) was deadlocked on thread | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
The issue was fixed in the cumulative update 4 (CU4) of SQL Server 2014.
https://support.microsoft.com/kb/2999197

Incorrect results may be returned when you use Option(Recompile) for queries inside a procedure and involves join to other tables and the joined table is updated from another transaction in SQL Server 2014
The issue was fixed in the cumulative update 4 (CU4) of SQL Server 2014.
https://support.microsoft.com/kb/2999197

When using SQL Server 2012 service broker as an initiator to send high number of messages to a remote target, a race condition might occur leading to an access violation and deadlocked schedulers and may cause service broker to stop working.
The issue was fixed in the cumulative update 4 (CU4) of SQL Server 2014.
https://support.microsoft.com/kb/2999197

When a query is run which contains common language runtime (CLR) functions in the WHERE clause against an indexed view, may cause an fatal exception and that session may get disconnected.
The issue was fixed in the cumulative update 4 (CU4) of SQL Server 2014.
https://support.microsoft.com/kb/2999197

When manual failover is performed on a mirrored database, you may notice that database takes a long time to recover and to come online on the new Principal server or the database stays in “In Recovery” status for a long time and does not assume the role of the mirror database on the new mirror server and at the same time, the new Principal database may also get into “Principal, Disconnected” state.
The issue was fixed in the cumulative update 4 (CU4) of SQL Server 2014.
https://support.microsoft.com/kb/2999197

In Merge replication when a custom stored procedure resolver is used to resolve conflicts, there may be additional characters added to the character type data after conflict resolution. Also the merge agent may fail and following error may be logged in the replmerg.log file
ERROR: ErrNo = 0x8004565a, ErrSrc = <null>, ErrType = 8, ErrStr = The Merge Agent failed because the schema of the article at the Publisher does not match the schema of the article at the Subscriber. This can occur when there are pending DDL changes waiting to be applied at the Subscriber. Restart the Merge Agent to apply the DDL changes and synchronize the subscription.
The issue was fixed in the cumulative update 4 (CU4) of SQL Server 2014.
https://support.microsoft.com/kb/2999197

With release of each new version and new service packs of SQL Server, new issues or bugs will surface and Microsoft will work on fixing high priority bugs. Above are some of the top known issues which were identified and fixed in Microsoft SQL Server 2014 CU4.

This is applicable on below versions of SQL Server

SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 

Leave a Reply

Your email address will not be published. Required fields are marked *