SQL Server 2012 SP2 – List of Bugs


Microsoft has announced SQL Server 2012 service pack 2 is available just a few days ago. Service packages are cumulative updates and upgrade all editions of SQL Server 2012. This service pack contains up to and including SQL Server 2012 Service Pack1 Cumulative Update 9 (CU9). Here is the list of the bugs which are fixed in SQL Server 2012 SP2. You can get additional information here.

VSTS bug number KB article number Description
1703014 2963382 FIX: Can’t connect to the server when you run a cube creation MDX query in SSAS 2012
2011247 2927741 FIX: Image is not displayed correctly in the webpage when you use DrillThrough action on an SSRS 2012 report
2034994 2963383 FIX: Text truncated when you use HPB renderer to view a report in SSRS 2012
1769469 2963384 FIX: SQL Server crashes when the log file of tempdb database is full in SQL Server 2012
1973168 2963386 FIX: SSRS 2012 fails with IsolatedStorageException when subscriptions exported to Excel worksheets are larger than 10 MB
1973196 2963388 FIX: SSRS 2012 cannot export a report that is larger than 10 MB to Excel format
787358 2963404 FIX: Rollback causes database to go to suspect mode in SQL Server 2012
1043717 2806979 FIX: Poor performance when you run a query against a table in an RCSI-enabled database in SQL Server 2012
1178585 2963412 New DMF sys.dm_fts_index_keywords_position_by_document in SQL Server 2012 SP2
1182241 2966520 FIX: New log files are not created when you restart the Reporting Services Windows Service in SSRS 2012 on January 1
1240848 2966519 FIX: No error message when log backup failed in SQL Server 2012
1253861 2936004 FIX: Visual Studio 2012 crashes because of access violation when the data source binding is completed in Report Viewer 2012 UI in local mode
1262029 2966522 FIX: File Share subscription doesn’t populate the description column in SSRS 2012
1481773 2966523 FIX: The “Name” drop-down list is empty when an SSRS 2012 report is specified
1419367 2964762 FIX: Event ID 22 or error 0xC1000016 will be logged when you use Discover command in SSAS 2012
2103903 2972285 FIX: Performance issues when you use SSISDB as your deployment store in SQL Server 2012
2021581 2965035 SSAS 2012 logging feature improvement in SQL Server 2012 Service Pack 2
203749 2952444 FIX: Poor performance when you use table variables in SQL Server 2012
2095064 2936328 FIX: Access violation occurs when you run CHECKTABLE or CHECKDB against a table that has persisted computed columns in SQL Server 2008 R2 or SQL Server 2012

Resolutions to the following issues are also included in SQL Server 2012 SP2.

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.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s