However, we recommend that you always install the latest cumulative update that is available.Īdditional hotfixes that are included in this cumulative update packageįIX: Missing logs for Analysis Services Processing tasks in SQL Server 20 Integration ServicesįIX: Memory gets exhausted when you run Power BI report that executes DAX query on SSAS 2014, 20 Multidimensional modeįalse error reporting when you execute the Test-SqlAvailabilityGroup cmdlet in SQL ServerįIX: Access violation when you compile a query and histogram amendment is enabled with default Cardinality Estimation in SQL Server 20įIX: Error occurs when you run sp_send_dbmail stored procedure that contains comma in sender email address and name in SQL ServerįIX: Access violations and unhandled exceptions when you set automatic seeding for secondary replica or Distributed Availability Group replica in SQL ServerįIX: Masked data is exposed when a query that uses sp_cursorfetch is run in SQL Server if Dynamic Data Masking is enabledįIX: Access violation when you run a query that uses the XML data type in SQL Server 2014, 20įIX: Transactions and log truncation may be blocked when you use Query Store in SQL Server 20įIX: Error occurs when the Database Encryption Key is longer than 3,456 bits in SQL Server 20įIX: “An unexpected exception occurred” when you run an MDX query after an XMLA query to process a dimension in SSASįIX: Deadlock occurs in SSAS 20 when you run a DAX query with time intelligence calculation in parallelįIX: The schedule changes to "Report-specific schedule" when you enable "Create cache snapshots on a schedule" for the report in SSRS 2016įIX: I/O error on a BPE file causes buffer time-out in SQL ServerįIX: Nested tablix shows small font or partial text in SSRS 2016 and later versionsįIX: Out of memory error occurs when Database Node Memory (KB) drops below 2 percent in SQL Server 20įIX: "Non-yielding" error occurs when there is a heavy use of prepared statements in SQL Server 20įIX: Restore of TDE-compressed backup is unsuccessful when backing up database to a 512-byte Emulation disk in SQL ServerįIX: SQL Server installation fails if one of the remote nodes is unreachable in a clusterįIX: High CPU usage when there are many batch requests in SQL Server 2016įIX: SQL Server service crashes when DBCC CHECKDB runs against a database that has a corrupted partitionįIX: Server crashes when you cancel DBCC CHECKDB against a large database in SQL Server 2016įIX: Columnstore Index build request may time out after 25 seconds though the memory grant time-out is configured in SQL Server 2016
Note After future cumulative updates are released for SQL Server 2016, this CU can be located and downloaded from the Microsoft Windows Update Catalog.
If the download page does not appear, contact Microsoft Customer Service and Support to obtain the cumulative update package. The following update is available from the Microsoft Download Center:ĭownload the latest cumulative update package for SQL Server 2016 SP2 now.
How to obtain this cumulative update package
We recommend that you upgrade your SQL Server installation to the latest SQL Server 2016 service pack. Just as for SQL Server service packs, we recommend that you test CUs before you deploy them to production environments. This includes supportability, manageability, and reliability updates. Historical data shows that a significant number of support cases involve an issue that has already been addressed in a released CU.ĬUs may contain added value over and above hotfixes. SQL Server CUs are certified to the same levels as Service Packs, and should be installed at the same level of confidence. Microsoft recommends ongoing, proactive installation of CUs as they become available:
Only the most recent CU that was released for SQL Server 2016 SP2 is available at the Download Center.Įach new CU contains all the fixes that were included with the previous CU for the installed version/Service Pack of SQL Server.
Cumulative updateĬumulative updates (CU) are now available at the Microsoft Download Center. This update contains fixes that were released after the initial release of SQL Server 2016 SP2. 1) for Microsoft SQL Server 2016 Service Pack 2 (SP2). This article describes Cumulative Update package 5 (CU5) (build number. SQL Server 2016 Developer SQL Server 2016 Enterprise SQL Server 2016 Enterprise Core SQL Server 2016 Standard SQL Server 2016 Business Intelligence SQL Server 2016 Express SQL Server 2016 Web More.