List of Bugs Fixed in SQL Server 2012 SP2 – PART 4
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 for Microsoft SQL Server 2012.
SQL Server MSDN KB Number 1374617
FIX: Shared components are installed in the wrong location when you implement a SQL Server 2008 Failover Cluster installation
SQL Server MSDN KB Number 1610447
Uninitialized object leads to crashes and potentially wrong results when executing DAX expressions with conditional calculations.
SQL Server MSDN KB Number 1610492
A simple DAX query returns unexpected results when you use PowerPivot v2 11.0.3000.0.
SQL Server MSDN KB Number 2060218
“ACTIONABLE_HEAP_CORRUPTION” when SSRS configuration file is parsed by using an invalid InstanceId.
SQL Server MSDN KB Number 2065570
NonYieldProcessTable record in RING_BUFFER_NONYIELD_PROCESSTABLE ring buffer does not have user and kernel process time.
SQL Server MSDN KB Number 2075161
Provides platform information in the log of SSRS 2012
SQL Server MSDN KB Number 1347204
FIX: Access Violation when you insert data into a table that has a column with a sequence default from a cross-database transaction in SQL Server 2012
SQL Server MSDN KB Number 1184332
If a tail log backup is performed against the model database, model database will freeze in restoring state during a server restart that will prevent the SQL Server from starting successfully. This is because Tempdb database could not be created during the server startup and you receive the following error message: “Database ‘
SQL Server MSDN KB Number 1243853
Error 3456 occurs when restoring the log backup of a bulk-logged DB where a new data file was added with an initial size greater than 64704KB.
SQL Server MSDN KB Number 1404999
When you drop of a database snapshot is issued in a session with a LOCK_TIMEOUT setting, a time-out error may occur followed by an assertion error.
SQL Server MSDN KB Number 1190211
Installation of SQL Server by using InstallShield ends up in a hang state. For more information, go to this Knowledge Base article.
SQL Server MSDN KB Number 1386073
After you install SQL Server 2012 SP2, when SQL Server is stopped from either configuration manager or service control manager, an informational message is logged to the SQL Server immediately after shutdown is issued. In earlier versions, we issued this messages after internal services, such as the .NET Framework, service broker, were stopped.
Hope this was helpful.
This is applicable for below versions of SQL Server
SQL Server 2014
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, Frequently asked questions, SQL Server Trainings