Search

Store Auto Slipstream Extracted Updates by Randy in Marin

Active

1
0
Sign in
to vote
Type: Suggestion
ID: 765825
Opened: 10/2/2012 5:33:09 PM
Access Restriction: Public
0
Workaround(s)
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"

Details (expand)

Product Language

English

Category

Setup

Proposed Solution

Provide a Boolean option to direct SETUP to store or use extracted updates in a folder - perhaps "UpdateCache". The source of the update can be online, WSUS, or the UpdateSource folder as it is now. If SETUP needs to extract an update, it is stored in the UpdateCache folder. If the update is already extracted, SETUP does not extract it again and uses the extracted version already in the UpdateCache folder.

Because each source (e.g., online, WSUS, or UpdateSource) can have a different set of updates available, metadata is needed to track which extracted updates are valid for a source. There can be up to three different sets of updates in the cache - one for each source (e.g., online-SP1-CU4 & wsus-SP1-CU3 & updatesource-RTM-CU6). However, there might be one common current update for all three sources (e.g., online-SP1-CU4 & wsus-SP1-CU4 & updatesource-SP1-CU4). There can be two sets as well - one different from the other two.

If a newer version of an update is cached, setup should update the metadata. If there are no sources referencing an extracted update, it should be deleted. For example, if RTM CU5 is cached from a new update place in the UpdateSource folder, remove any metadata for this source from other extracted updates, if present. Extracted updates left without any sources are deleted.

It is safe to clear the UpdateCache folder as it would be reloaded as needed.

If the UpdateCache option is not provided, SETUP ignores the UpdateCache folder.

Primary Benefit

Improved Installation

Other Benefits

Administration could also be improved if an online update can be used to populate the UpdateSource folder. I can manually get the updates, but it would be nice to have the setup do this for me. Allow us to place the extracted update into the UpdateSource folder?

Virtualization

 
File Attachments
0 attachments
Sign in to post a comment.
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.

thanks,
[SQL Server Team]
Sign in to post a workaround.