List of Bugs Fixed in SQL Server 2012 SP2 CU7 – Part 1

SQLServerF1

With every release of SQL Server product or subsequent service packs or Cumulative updates, new bugs are encountered or discovered. Below are some of the bugs which were fixed with the release of Service Pack 2 Cumulative Update 7 (SP 2 CU 7) for Microsoft SQL Server 2012.

SQL Server MSDN KB Number 3983191
FIX: The changes in Oracle databases are not replicated to SQL Server 2012 or SQL Server 2014 databases correctly Integration Services
SQL Server MSDN KB Number 3030352
FIX: The change table is ordered incorrectly for updated rows after you enable change data capture for a Microsoft SQL Server 2012 database SQL service
SQL Server MSDN KB Number 3052461
FIX: Some attributes in element are ignored when you transform XML file in SSIS 2012 Integration Services

SQL Server MSDN KB Number 3062001
FIX: “Failed to create kernel event for collection set” error occurs when you use Data Collection in SQL Server 2012 Management Tools
SQL Server MSDN KB Number 3061215
FIX: “Cannot read 8 bytes from file” error occurs when you use SSIS 2012 Integration Services
SQL Server MSDN KB Number 3064454
FIX: Hash or merge join hints may be ignored when you execute a query in SQL Server 2012 SQL performance

SQL Server MSDN KB Number 3065060
FIX: “Unable to create restore plan due to break in the LSN chain” error when you restore differential backup in SSMS Management Tools
SQL Server MSDN KB Number 3068351
FIX: ROLAP Distinct Count on data source is not started when it is running from SSAS 2012 to back-end SQL Server 2014 Analysis Services
SQL Server MSDN KB Number 3068359
FIX: “Cannot find the OLAP cube Model” error when you update the pivot table in a SharePoint document in SQL Server 2012 Analysis Services

Hope this was helpful.

This is applicable for below versions of SQL Server

SQL Server 2014

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

 

Leave a Reply

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