Contents
Is there an issue with SQL Server 2017 CU 20?
Under certain circumstances, there is a known uninstallation issue that affects SQL Server 2017 CU 20. After you uninstall CU 20, SQL Server doesn’t come online, and the following error entry is logged in the SQL Server log:
Do you need to install cus with SQL Server?
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 according to these guidelines:
How to uninstall cumulative update in SQL Server 2017?
In Control Panel, open the Programs and Features item, and then select View installed updates. Locate the entry that corresponds to this cumulative update package under SQL Server 2017. Press and hold (or right-click) the entry, and then select Uninstall. To uninstall this CU on Linux, you must roll back the package to the previous version.
Where can I get SQL Server 2017 update?
Only the most recent CU that was released for SQL Server 2017 is available at the Download Center. CU packages for Linux are available at https://packages.microsoft.com/. Each new CU contains all the fixes that were included with the previous CU for the installed version of SQL Server.
Where can I find cumulative updates for SQL Server?
Cumulative updates (CU) are now available at the Microsoft Download Center. Only the most recent CU that was released for SQL Server 2017 is available at the Download Center. CU packages for Linux are available at https://packages.microsoft.com/.
How big is the latest SQL Server update?
File Size: 528.6 MB. The latest Cumulative Update (CU) download is the most recent CU released for SQL Server 2017 and contains all updates released since the release of SQL Server 2017 RTM.
Is there a fix for SQL Server 2017?
SQL Server 2017 CU21 or any later CU release contains the fix. When you deploy an update to a hybrid environment (such as AlwaysOn, replication, cluster, and mirroring), we recommend that you refer to the following articles before you deploy the update: Install the update on the passive node.