|
| 1 | +--- |
| 2 | +title: "Slipstream Installation for SQL Server" |
| 3 | +description: This article describes how to use the slipstream installation process to install SQL Server and all available updates. |
| 4 | +author: prmadhes-msft |
| 5 | +ms.author: prmadhes |
| 6 | +ms.reviewer: randolphwest, jopilov |
| 7 | +ms.date: 08/21/2025 |
| 8 | +ms.service: sql |
| 9 | +ms.subservice: install |
| 10 | +ms.topic: install-set-up-deploy |
| 11 | +monikerRange: ">=sql-server-2016" |
| 12 | +ms.custom: |
| 13 | + - intro-installation |
| 14 | +--- |
| 15 | +# Slipstream installation for SQL Server |
| 16 | + |
| 17 | +[!INCLUDE [SQL Server -Windows Only](../../includes/applies-to-version/sql-windows-only.md)] |
| 18 | + |
| 19 | +Slipstream installation is the process of integrating cumulative updates (CUs) into the [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] setup process. This method ensures that [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] is installed with the latest fixes and improvements in a single operation, without requiring a post-installation patch. |
| 20 | + |
| 21 | +Slipstreaming is useful for: |
| 22 | + |
| 23 | +- Avoiding known setup issues in base media |
| 24 | + |
| 25 | +- Reducing deployment time and manual effort by performing installation and patching in one operation and helping avoid extra operating system reboots. |
| 26 | + |
| 27 | +## How slipstreaming works |
| 28 | + |
| 29 | +During setup, you run [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] installation with the `/UpdateEnabled=True` parameter to enable update integration, and specify the folder containing the desired CU using `/UpdateSource`. |
| 30 | + |
| 31 | +For example: |
| 32 | + |
| 33 | +```console |
| 34 | +setup.exe /Action=Install /UpdateEnabled=True /UpdateSource="C:\SQLUpdates" |
| 35 | +``` |
| 36 | + |
| 37 | +This example command line operation tells Setup to use the updated binaries from the specified folder instead of the original base media, applying them during the installation process. |
| 38 | + |
| 39 | +## Guidance for using slipstream |
| 40 | + |
| 41 | +- You should integrate the latest cumulative updates into the installation media to ensure the instance starts with the most stable and secure configuration. |
| 42 | + |
| 43 | +- Test slipstream installations in a staging environment before deploying to production. |
| 44 | + |
| 45 | +- Use consistent update packages across all servers in an environment to ensure compatibility. |
| 46 | + |
| 47 | +- If adding features later, use matching installation media or apply the same cumulative update to the existing instance. |
| 48 | + |
| 49 | +## When to use slipstream |
| 50 | + |
| 51 | +- You set up new instances of [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] and want them patched during installation to avoid unnecessary restarts. |
| 52 | + |
| 53 | +- You encounter setup failures with base installation media and need patched setup binaries. |
| 54 | + |
| 55 | +- You deploy [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] across multiple machines and want a consistent, reliable experience. |
| 56 | + |
| 57 | +## Slipstream installation steps |
| 58 | + |
| 59 | +### Step 1: Create a folder to store the SQL updates |
| 60 | + |
| 61 | +Create a local folder to store the update files. For example: |
| 62 | + |
| 63 | +```powershell |
| 64 | +New-Item -ItemType "Directory" -Path "C:\SQLUpdates" -Force |
| 65 | +``` |
| 66 | + |
| 67 | +### Step 2: Download the latest update |
| 68 | + |
| 69 | +Download the [latest cumulative update](/troubleshoot/sql/releases/download-and-install-latest-updates) for your version of [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] into the newly created folder. |
| 70 | + |
| 71 | +### Step 3: Run the installer with slipstream parameters |
| 72 | + |
| 73 | +Run [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] Setup using the following command: |
| 74 | + |
| 75 | +```powershell |
| 76 | +C:\SqlSetupMedia\setup.exe /Action=Install /UpdateEnabled=True /UpdateSource="C:\SQLUpdates" |
| 77 | +``` |
| 78 | + |
| 79 | +| Parameter | Description | |
| 80 | +| --- | --- | |
| 81 | +| `/Action=Install` | Tells [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] Setup to start the installation process. If you leave this parameter out, Setup only opens the Installation Center, and ignores other parameters like update paths. | |
| 82 | +| `/UpdateEnabled=True` | Enables update detection. It tells Setup to look for and include any available updates (like a cumulative update) during the installation. | |
| 83 | +| `/UpdateSource=<location>` | Points to the folder where your update files (CU) are stored. | |
| 84 | + |
| 85 | +For more information about setup parameters, see [Install and configure SQL Server on Windows from the command prompt](install-sql-server-from-the-command-prompt.md) |
| 86 | + |
| 87 | +### Step 4: Complete setup |
| 88 | + |
| 89 | +Proceed through the setup wizard as usual. |
| 90 | + |
| 91 | +During installation, you see confirmation that the update was integrated. |
| 92 | + |
| 93 | +:::image type="content" source="media/install-sql-server-using-slipstream/installation-screen.png" alt-text="Screenshot showing the results."::: |
| 94 | + |
| 95 | +### Step 5: Verify installation success |
| 96 | + |
| 97 | +After installation, the applied CU will be visible in: |
| 98 | + |
| 99 | +- **Programs and Features** > **Installed Updates** (from the Windows Start menu) |
| 100 | + |
| 101 | +- [SQL Server features discovery report](validate-a-sql-server-installation.md#run-sql-server-features-discovery-report) |
| 102 | + |
| 103 | +- Setup log (`Summary.txt`) under `Patch Level`. For more information, see [View and read SQL Server Setup log files](view-and-read-sql-server-setup-log-files.md). |
| 104 | + |
| 105 | + ```output |
| 106 | + Overall summary: |
| 107 | + Final result: Passed |
| 108 | + Exit code (Decimal): 0 |
| 109 | + Start time: 2025-08-17 11:55:45 |
| 110 | + End time: 2025-08-17 12:14:24 |
| 111 | + Requested action: Install |
| 112 | +
|
| 113 | + Machine Properties: |
| 114 | + Machine name: <machine-name> |
| 115 | + Machine processor count: 8 |
| 116 | + OS version: Microsoft Windows Server 2019 Standard (10.0.17763) |
| 117 | + OS service pack: |
| 118 | + OS region: United States |
| 119 | + OS language: English (United States) |
| 120 | + OS architecture: X64 |
| 121 | + Process architecture: 64 Bit |
| 122 | + OS clustered: No |
| 123 | +
|
| 124 | + Product features discovered: |
| 125 | + Product Instance Instance ID Feature Language |
| 126 | +
|
| 127 | + Package properties: |
| 128 | + Description: Microsoft SQL Server 2019 |
| 129 | + ProductName: SQL Server 2019 |
| 130 | + Type: RTM |
| 131 | + Version: 15 |
| 132 | + Installation location: C:\SQL Server\SQL 2019\SQLFull_ENU\x64\setup\ |
| 133 | + Installation edition: Enterprise Edition: Core-based Licensing |
| 134 | +
|
| 135 | + Slipstream: True |
| 136 | + SP Level 0 |
| 137 | + Patch Level: 15.0.4430.1 |
| 138 | +
|
| 139 | + Product Update Status: |
| 140 | + Success: KB 5054833 |
| 141 | +
|
| 142 | + Product Updates Selected for Installation: |
| 143 | + Title: Hotfix Pack |
| 144 | + Knowledge Base Article: KB 5054833 |
| 145 | + Version: 15.0.4430.0 |
| 146 | + Architecture: x64 |
| 147 | + Language: All |
| 148 | + Update Source: C:\SQL Server\SQL 2019\SQLFull_ENU\CU |
| 149 | + ``` |
| 150 | + |
| 151 | +## How to identify a slipstream installation |
| 152 | + |
| 153 | +To confirm that slipstreaming was used to run Setup: |
| 154 | + |
| 155 | +- The setup wizard displays rules such as: |
| 156 | + |
| 157 | + ```output |
| 158 | + Update Setup Media Language Rule |
| 159 | + ``` |
| 160 | + |
| 161 | +- The install log includes lines such as: |
| 162 | + |
| 163 | + ```output |
| 164 | + Slipstream: True |
| 165 | + SP Level 0 |
| 166 | + Patch Level: 15.0.4430.1 |
| 167 | + ``` |
| 168 | + |
| 169 | +- Run the [SQL Server features discovery report](validate-a-sql-server-installation.md#run-sql-server-features-discovery-report) to verify version levels. |
| 170 | + |
| 171 | +## Remarks |
| 172 | + |
| 173 | +If Setup fails, review the failure details in the logs file located at `C:\Program Files\Microsoft SQL Server\<nn>\Setup Bootstrap\Log\Summary.txt`, where `<nn>` is the version you're installing. For more information, see [View and read SQL Server Setup log files](view-and-read-sql-server-setup-log-files.md). |
| 174 | + |
| 175 | +Here's an example of a failed slipstream installation. |
| 176 | + |
| 177 | +```output |
| 178 | +Overall summary: |
| 179 | + Final result: Failed: see results below |
| 180 | + Exit code (Decimal): -2068643839 |
| 181 | + Start time: 2025-08-17 09:55:12 |
| 182 | + End time: 2025-08-17 10:03:01 |
| 183 | + Requested action: Install |
| 184 | +
|
| 185 | +Setup completed with required actions for features. |
| 186 | +Troubleshooting information for those features: |
| 187 | + Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again. |
| 188 | +``` |
| 189 | + |
| 190 | +Slipstreaming doesn't eliminate the need to monitor future updates post-installation. |
| 191 | + |
| 192 | +## Related content |
| 193 | + |
| 194 | +- [Install and configure SQL Server on Windows from the command prompt](install-sql-server-from-the-command-prompt.md) |
| 195 | +- [Install SQL Server from the Installation Wizard (Setup)](install-sql-server-from-the-installation-wizard-setup.md) |
| 196 | +- [Install SQL Server using a configuration file](install-sql-server-using-a-configuration-file.md) |
0 commit comments