SQL Server 2012 SP2 – List of Bugs

VSTS bug number
Description

950185
Improved messaging around processing errors and warnings when you work with large HTML reports.

950189
Improved messaging around processing errors and warnings when you work with reports with large number of parameters.

994470
Incorrect results when you work with block mode unary operators.

1041277
DPM’s full backup on the server with AlwaysOn secondary will be converted to copy_only backup.

1278767
The value of tabular instance perfmon counters: Memory\VertiPaq <TypeName> KB is always 0.

1355346
The end SCOPE statement does not match the opening SCOPE statement.

1374617
FIX: Shared components are installed in the wrong location when you implement a SQL Server 2008 Failover Cluster installation

1610447
Uninitialized object leads to crashes and potentially wrong results when executing DAX expressions with conditional calculations.

1610492
A simple DAX query returns unexpected results when you use PowerPivot v2 11.0.3000.0.

2060218
“ACTIONABLE_HEAP_CORRUPTION” when SSRS configuration file is parsed by using an invalid InstanceId.

2065570
NonYieldProcessTable record in RING_BUFFER_NONYIELD_PROCESSTABLE ring buffer does not have user and kernel process time.

2075161
Provides platform information in the log of SSRS 2012

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

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 ‘<DatabaseName>‘ cannot be opened”

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.

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.

1190211
Installation of SQL Server by using InstallShield ends up in a hang state. For more information, go to this Knowledge Base article.

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.