Top Known Issues with Microsoft SQL Server 2014 CU3

SQLServerF1

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. Below are some of the top known issues which were identified and fixed in Microsoft SQL Server 2014 CU3.

– In Microsoft SQL Server 2014, if you are running a query which involves multiple table joins, and if any of the tables referenced in the query has Clustered Columnstore Index, then you may notice significant poor performance with the query because of missing Clustered Column Store Index segment elimination.

o Micorsoft has identified this issue and has released a fix for the same.
http://support.microsoft.com/kb/2984923/en-us
o Either Apply this fix if this is business critical issue, else apply latest available Cumulative Update or Service Pack.

– If you have defined a temporary variable and populated huge number of row into it, and then if you are using this temp variable in queries where you join this with other tables, then you may notice slow performance problems with the query.

o Microsoft has identified this issue and has released a fix for the same in CU3 of SQL Server 2014.
http://support2.microsoft.com/kb/2952444

– You may receive above error when you try to open memory-optimized table template from SQL Server Management Studio (SSMS) from a remote client machine and using SQL Server Authentication to connect to SSMS.
Failed to connect to Server ""
The target principal Name is incorrect. Cannot generate SSPI context

o Microsoft has identified this issue and has released a fix for the same in CU3 of SQL Server 2014.
http://support2.microsoft.com/kb/2952444

– If a database which is part of AlwaysOn Availability Group and if this database consists of an In-Memory Table in new SQL Server and while you try to insert or update which affects multiple rows in one transaction on this table may lead to an “non-yielding scheduler” error. This will then result in the failover of the AlwaysOn Availability Group because the dump file generation takes a long time to complete.

o Microsoft has identified this issue and has released a fix for the same in CU3 of SQL Server 2014.
http://support2.microsoft.com/kb/2952444

– Access Violation exception and memory stack dump will be generated in SQL Server 2014, when you create a user-defined table and add some extended properties at the column level and then tried to query sys.extended_properties system table.

o Microsoft has identified this issue and has released a fix for the same in CU3 of SQL Server 2014.
http://support2.microsoft.com/kb/2952444

– You will receive below error when you have a FileTable or FILESTREAM in SQL Server 2014, and you have defined the MAXSIZE of FILESTREAM data to UNLIMITED and when the used size of FileTable when the FILESTREAM container size has reached 32 terabytes (TB) and then you tried to insert more data.
error 1105 Could not allocate space for object ‘‘ in database ‘’ because the ‘‘ filegroup is full.

o Microsoft has identified this issue and has released a fix for the same in CU3 of SQL Server 2014.
http://support2.microsoft.com/kb/2952444

– Log Reader Agent crashes by causing an access violation exception and memory stack dump during the initialization of the log reader agent in Transactional Replication.

o Microsoft has identified this issue and has released a fix for the same in CU3 of SQL Server 2014.
http://support2.microsoft.com/kb/2952444

– In SQL Server 2014, if you have a table that is partitioned and also has a clustered columnstore index and when you try to create an indexed view on this table, you will receive the error message: Internal Query Processor Error: The query processor could not obtain access to a required interface.

o Microsoft has identified this issue and has released a fix for the same in CU3 of SQL Server 2014.
http://support2.microsoft.com/kb/2952444

– By default “Auto Create Statistics” databases option is enabled on all databases. In SQL Server 2014, if you try to create a natively compiled stored procedure and if internally triggers the automatic creation of missing statistics, then a self-deadlock can occur which can significantly increases the compilation time.

o Microsoft has identified this issue and has released a fix for the same in CU3 of SQL Server 2014.
http://support2.microsoft.com/kb/2952444

– In SQL Server 2014, if you created a memory-optimized table variables outside of the natively compiled stored procedures, then a LCK_M_SCH_M (schema modify lock) is taken on the corresponding memory-optimized table, during destructing of the table variable, this any concurrent declaration of memory-optimized table variables outside of natively compiled stored procedures are blocked.

o Microsoft has identified this issue and has released a fix for the same in CU3 of SQL Server 2014.
http://support2.microsoft.com/kb/2952444

– In SQL Server 2014, If “UPDATE STATISTICS” is performed on a computed column that contains the “ISNULL” function then it will cause an access violation exception and generated a memory stack dump.

o Microsoft has identified this issue and has released a fix for the same in CU3 of SQL Server 2014.
http://support2.microsoft.com/kb/2952444

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 *