SQL Server 2017 CU30: Features, Fixes, and FAQs
How to Download and Install Cumulative Update 30 for SQL Server 2017
If you are using SQL Server 2017, you may want to download and install the latest cumulative update (CU) for your version. In this article, we will explain what is CU30 for SQL Server 2017, why you need to install it, what are the improvements and fixes included in it, how to download it, how to install it, and how to verify the installation.
download cumulative update 30 for sql server 2017
What is Cumulative Update 30 for SQL Server 2017?
Cumulative Update 30 (CU30) for SQL Server 2017 is a package of updates that contains all the fixes that were released after the initial release of SQL Server 2017. It was released on July 13, 2022 by Microsoft. It updates the components of SQL Server 2017 to the following builds:
SQL Server - Product version: 14.0.3451.2, file version: 2017.140.3451.2
Analysis Services - Product version: 18.104.22.168, file version: 2017.140.249.90
Cumulative updates are incremental, which means that each new CU contains all the fixes from the previous CUs. Therefore, you only need to install the latest CU to get all the fixes for your version of SQL Server.
Why do you need to install Cumulative Update 30 for SQL Server 2017?
You need to install CU30 for SQL Server 2017 if you want to improve the performance, reliability, security, and compatibility of your SQL Server instance. CU30 contains eight fixes that address various issues in different areas of SQL Server, such as high availability, SQL engine, and service broker.
Some of the issues that are fixed by CU30 are:
A latch time-out occurs and the IOCP listener stalls when Service Broker connects to an endpoint by using database mirroring.
The lock escalation policy for the change tracking table is matched to that of the base table.
An access violation occurs when you try to truncate specific partitions of a table by using the $Partition function if the function name or table name does not exist.
Dropping temp tables causes an unresolved deadlock and dump file in some rare cases.
An assertion failure occurs when your query contains the MERGE statement.
The online index rebuild can't finish when you use the simple recovery model.
Error 2706 occurs when you run DBCC CHECKDB WITH EXTENDED_LOGICAL_CHECKS against a database by using the Table-Valued Function (TVF) that uses indexes.
The query optimizer generates a suboptimal plan when you use a TVF with a parameterized TOP clause.
For more details about these fixes, you can refer to .
How to install CU30 for SQL Server 2017 on Windows
SQL Server 2017 latest cumulative update package download link
KB5013756 - Fixes and improvements in SQL Server 2017 CU30
SQL Server 2017 CU30 version and file information
Known issues and workarounds for SQL Server 2017 CU30
SQL Server 2017 CU30 release date and support lifecycle
How to uninstall SQL Server 2017 CU30 if needed
SQL Server 2017 CU30 compatibility and requirements
How to verify the installation of SQL Server 2017 CU30
SQL Server 2017 CU30 performance and stability enhancements
How to troubleshoot SQL Server 2017 CU30 installation errors
SQL Server 2017 CU30 security and vulnerability fixes
How to apply SQL Server 2017 CU30 to Analysis Services
SQL Server 2017 CU30 impact on database mirroring and service broker
How to use trace flags with SQL Server 2017 CU30
SQL Server 2017 CU30 changes in lock escalation policy for change tracking tables
How to avoid access violation when truncating partitions with $Partition function in SQL Server 2017 CU30
How to resolve deadlock and dump file issues when dropping temp tables in SQL Server 2017 CU30
How to fix assertion failure and online index rebuild issues with MERGE statement in SQL Server 2017 CU30
How to run DBCC CHECKDB with EXTENDED_LOGICAL_CHECKS against TVF indexes in SQL Server 2017 CU30
How to download and install SQL Server 2017 CU31 - the latest cumulative update as of now
How to check the current version and build of SQL Server 2017 installed on your system
How to get notified of new cumulative updates for SQL Server 2017
How to report feedback or issues with SQL Server 2017 cumulative updates
How to request a hotfix for a specific issue in SQL Server 2017 that is not fixed by cumulative updates
How to backup and restore databases before and after applying SQL Server 2017 cumulative updates
How to test SQL Server 2017 cumulative updates in a non-production environment before deploying them
How to use the slipstream method to install SQL Server 2017 with the latest cumulative update
How to upgrade from an older version of SQL Server to SQL Server 2017 with the latest cumulative update
How to use the servicing model tool (SQLSVCUtil.exe) to manage cumulative updates for SQL Server 2017
How to configure automatic updates for SQL Server 2017 through Windows Update or WSUS
How to use PowerShell scripts or command-line tools to install or uninstall SQL Server 2017 cumulative updates
How to monitor the health and performance of SQL Server 2017 after applying cumulative updates
How to use the query store feature to compare query plans and performance before and after applying SQL Server 2017 cumulative updates
How to use the dynamic management views (DMVs) and functions (DMFs) to get information about the applied cumulative updates for SQL Server 2017
How to download Cumulative Update 30 for SQL Server 2017?
You can download CU30 for SQL Server 2017 from two sources:
From the official Microsoft website
You can go to and click on the Download button. You will be asked to select the files that you want to download. You can choose the files that match your SQL Server edition and language. For example, if you have SQL Server 2017 Standard Edition in English, you can select the following files:
After you select the files, click on Next and save them to your preferred location.
From the Microsoft Update Catalog
You can also download CU30 for SQL Server 2017 from the . You can search for the update by using its KB number (5013756) or its title (Cumulative Update 30 for SQL Server 2017). You will see a list of files that are available for download. You can filter the list by product, classification, or last updated date. You can also sort the list by title, size, or date. You can select the files that match your SQL Server edition and language and click on Download. You will see a pop-up window with a link to download each file. You can save them to your preferred location.
How to install Cumulative Update 30 for SQL Server 2017?
Before you install CU30 for SQL Server 2017, you need to consider some prerequisites and recommendations:
Prerequisites and recommendations
You must have SQL Server 2017 installed on your computer. You can check your SQL Server version by using SQL Server Management Studio or Transact-SQL.
You must have administrative privileges on your computer to run the setup program.
You must back up your databases and any other important data before you install the update.
You must close any applications that are using SQL Server before you install the update.
You must restart your computer after you install the update.
You must apply the update to all instances of SQL Server 2017 on your computer.
You must test the update in a non-production environment before you deploy it in a production environment.
Steps to install the update
The steps to install CU30 for SQL Server 2017 are as follows:
Run the SQLServer2017-KB5013756-x64.exe file that you downloaded. This will extract the files to a temporary folder.
Navigate to the temporary folder and run the setup.exe file. This will launch the SQL Server Installation Center.
Select Maintenance from the left pane and then select Install SQL Server updates from the right pane.
The setup program will scan your computer for any instances of SQL Server 2017 that are eligible for the update. Select the instances that you want to update and click on Next.
The setup program will check for any rules or requirements that need to be met before installing the update. If there are any issues, resolve them and click on Next.
The setup program will show you a summary of the actions that will be performed. Review them and click on Update.
The setup program will install the update on the selected instances of SQL Server 2017. You can monitor the progress and status of the installation.
When the installation is complete, click on Close. The setup program will prompt you to restart your computer. Click on Yes to restart your computer.
How to verify the installation of Cumulative Update 30 for SQL Server 2017?
After you install CU30 for SQL Server 2017, you can verify that it was installed successfully by using one of these methods:
By using SQL Server Management Studio
You can use SQL Server Management Studio (SSMS) to check the version and build number of your SQL Server instance. To do this, follow these steps:
Open SSMS and connect to your SQL Server instance.
In Object Explorer, right-click on your server name and select Properties.
In the General page, look for Product version and Product level. They should show 14.0.3451.2 a