4

I'd like to take the latest version of SQL Server (SQL Standard, 15.0.2000.5), and apply the latest CU to it so that I have a single installer, thus reducing the size of the resulting package. The custom installer that I'm developing packages the SQL Server installer, and thus reducing the size by several hundred MB is important.

In previous versions of SQL Server, it was possible to create a single merged media output folder using the /PCUSOURCE and /CUSOURCE parameters, however this seems to have been removed in SQL Server 2014 (See "Slipstream Functionality" here). The alternative provided is to use the /UpdateSource flag, however this approach only allows for the simultaneous application of patches at the time of installation (by bundling the CU media with the original installation media). Further, the /ACTION=PrepareImage facilitates a SysPrep installation, not a slipstreamed update to the install media.

So, is there a way to update the installation media of SQL Server Standard 2019 with CU patches such that there's a single (reduced-size) installation media bundle?

| improve this question | |
  • May i know issue with using /UpdateSource it works just fine. Does the fact that it simultaneously patches SQL Server is a matter of concern for you ? – Shanky Mar 27 at 16:52
  • @Shanky When I experimented with the /UpdateSource flag, the installation procedure wanted me to proceed all the way toward doing an installation on a machine. What I want is a reduced-size single installation bundle that can be deployed multiple times. My main goal is to have the smallest possible media bundle (fewer MB) with the latest updates. – CJBS Mar 28 at 2:41
  • So your goal is to combine all the latest SP/CU into SQL Server installation file, keeping it small as possible, but you do not want to install it ? – Shanky Mar 28 at 4:34
  • @Shanky Correct. This used to be possible through the slipstreaming process, which integrated the SP/CUs into the original media with a combined size that was smaller than the sum of the two parts. – CJBS Mar 28 at 6:05
  • 1
    I have the same goal, except with the Express edition, where it seems incredibly silly to distribute a 600MB patch file with a 230MB full db install. It used to be possible to slipstream that all together into a single ~240MB installer. – Miral Apr 9 at 2:15

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.