Store Auto Slipstream Extracted Updates - by Randy in Marin

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 765825 Comments
Status Closed Workarounds
Type Suggestion Repros 0
Opened 10/2/2012 5:33:09 PM
Access Restriction Public


Please allow the auto slipstream feature of SETUP to store and reuse extracted updates.  Currently, SETUP can download and extract updates every time it is used.  When an UpdateSource folder is provided, the SETUP will not need to download the updates, but it will still extract the update each time it is used.  With a network install used by many developers, the extract of the same update is done many times needlessly.  

I'm not referring to saving the original update (e.g., SQLServer2012-KB2723749-x64.exe).  The extracted update can be manually created via /x: option.  For example, 

SQLServer2012-KB2723749-x64.exe /quiet /x:"path"

Sign in to post a comment.
Posted by Randy in Marin on 6/13/2014 at 2:44 PM
I just got SQL 2012 SP2. Still extracts every time I use it from the network install. I noticed the extract is to a temp folder. Perhaps it is enough to specify a location that is not temporary? The location can store the last SP and CU packages extracted. If a file in ".\UPDATES" will be used, check if a valid match (MD5 check?) is already in cache. If so, use the cached files. If not, extract item to cache, replacing any prior SP or CU cached. This should be enough since only the latest update is used.

;SQL Server 2012 Configuration File

Another option, add PCUEXTRACT and CUEXTRACT options to specify manually extracted SP and CU media. Then setup can do the slipstream with these if appropriate (e.g., media at or later than what is in ".\UPDATES").

SQL Server 2012 Configuration File

Or do both to cover all bases. Cache it if it's not available in UPDATECACHE, PCUEXTRACT, or CUEXTRACT. Perhaps the SP has been manually extracted, but we want any CU to be automatically cached?

Posted by Microsoft on 10/25/2012 at 1:06 PM
Hi Randy, thanks for taking the time to report this issue. We will take this feature request under consideration for a future release of SQL Server.

[SQL Server Team]