List of Bugs Fixed in SQL Server 2014 SP1 CU1 – Part 6

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 1 Cumulative Update 1 (SP 1 CU1) for Microsoft SQL Server 2014.

SQL Server MSDN KB Number 3025845
FIX: The transaction isolation level is reset incorrectly when the SQL Server connection is released in SQL Server 2014 SQL service
SQL Server MSDN KB Number 3026083
FIX: SOS_CACHESTORE spinlock contention on ad hoc SQL Server plan cache causes high CPU usage in SQL Server 2012 or 2014 SQL service
SQL Server MSDN KB Number 3027232
FIX: Error when you schedule data refresh by defining Secure Store ID in SQL Server PowerPivot for SharePoint 2013 Analysis Services

SQL Server MSDN KB Number 3030041
FIX: Error occurs when you connect to the database engine after you install CU4 for SQL Server 2014 Setup & Install
SQL Server MSDN KB Number 3030325
FIX: The scheduled refresh only occurs every other day instead of every day in SQL Server 2014 PowerPivot data refresh Analysis Services
SQL Server MSDN KB Number 3030326
FIX: Entries are no longer recorded on history page when you customize data refresh in PowerPivot for SharePoint 2013 Analysis Services

SQL Server MSDN KB Number 3030619
FIX: Incorrect data returned when you query the DATE column in SQL Server 2014 SQL service
SQL Server MSDN KB Number 2999809
FIX: Poor performance when a query contains table joins in SQL Server 2014 Management Tools
SQL Server MSDN KB Number 3034615
FIX: Memory leak occurs when you run DBCC CHECKDB against a database in SQL Server 2014 SQL service
SQL Server MSDN KB Number 3035071
FIX: Error when you run a query that contains “Use database_name” or “Execute Stored_Procedure_name” command Management Tools

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

 

List of Bugs Fixed in SQL Server 2014 CU6 – Part 5

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 Cumulative update package (CU) 6 for Microsoft SQL Server 2014.

MSDN Support KB Article 3030619
FIX: Incorrect data returned when you use DATE data type as a qualifier in a query in SQL Server 2014 SQL service
MSDN Support KB Article 3032067
FIX: Access denied when a newly added user browses to an MDS website in SQL Server 2014 MDS
MSDN Support KB Article 3032068
FIX: No MDSTrace.log file is generated after you enable tracing in the MDS 2014 web.config file MDS
MSDN Support KB Article 3032087
FIX: Cannot show requested dialog after you connect to the latest SQL Database Update V12 (preview) with SQL Server 2014 Management Tools

MSDN Support KB Article 3034297
FIX: Cannot close the connections made by sqlagent.exe when SQL Server and SQL Server Agent run for several days Management Tools
MSDN Support KB Article 3034615
FIX: Memory leak occurs when you run DBCC CHECKDB against a database in SQL Server 2014 SQL service
MSDN Support KB Article 3034679
FIX: AlwaysOn availability groups are reported as NOT SYNCHRONIZING High Availability
MSDN Support KB Article 3035071
FIX: Error when you run a query that contains “Use database_name” or “Execute Stored_Procedure_name” command Management Tools

MSDN Support KB Article 3035077
FIX: Cannot enable the change tracking in Azure SQL Database V12 that supports change tracking Management Tools
MSDN Support KB Article 3035165
FIX: Error 8646 when you run DML statements on a table with clustered columnstore index in SQL Server 2014 SQL service
MSDN Support KB Article 3036328
FIX: The value of statement_start_offset column is incorrect in DMV sys.dm_exec_requests in SQL Server 2014 SQL service
MSDN Support KB Article 3036330
FIX: Cannot use SQL Server 2014 SQL Profiler to connect to an instance of SQL Server 2005 Management Tools

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