Creating a merged (slipstreamed) drop containing SQL Server 2008 RTM + Service Pack 1

Servicing SQL Server 2008 Express

SQL Server Setup — Thu, 26 Feb 2009 07:36:11 GMT

The SQL Server 2008 Express Service Pack 1 – CTP has been released.  The internal workings and layout

re: SQL Server 2008, creating a merged (slipstreamed) drop

petersad — Thu, 26 Feb 2009 19:15:23 GMT

Thanks for giving it a try. For the CTP release, it is important to extract in the correct order as you pointed out. We'll be make setup.exe x86 for the final release so the order won't matter. You should be able to run with /QS and the configuration file, so let me know if you have further questions.

re: SQL Server 2008, creating a merged (slipstreamed) drop

wesclark — Fri, 27 Feb 2009 02:28:52 GMT

I got the unattended install working for capturing the configuration.ini file from the manual install. The only difference is that

; The directory for the extracted service pack files used to update the setup media.

PCUSOURCE="\\Files\network\downloads\Database\SQLServer2008\DeveloperEditionWithSP1\PCU"

replaced

MEDIASOURCE="\\files\network\downloads\Database\SQLServer2008\DeveloperEdition\"

How do I service SQL Server 2008

SQL Server Setup — Fri, 27 Feb 2009 02:55:54 GMT

The purpose of this blog is to help you determine how to update an existing installation of SQL Server

SQL Server 2008, basic slipstream steps

SQL Server Setup — Tue, 03 Mar 2009 02:17:39 GMT

Starting in SQL Server 2008 Service Pack 1, you can update the product using our "Slipstream"

How to fix your SQL Server 2008 Setup before you run setup (Part II)....

CSS SQL Server Engineers — Tue, 17 Mar 2009 16:49:09 GMT

Last year you might have read my post where I showed you how to patch setup for RTM for SQL Server 2008

SQL Server 2008 Service Pack 1 is Released!

SQL Server Setup — Wed, 08 Apr 2009 07:15:52 GMT

You can find SP1 here . This service pack makes available Slipstream and SP uninstall .   

SQL Server 2008 sp1 集成安装

rabbler — Wed, 08 Apr 2009 12:18:28 GMT

SQLServer2008,basicslipstreamsteps[UpdatedonApril7th,alongwiththeavailabilityofSQLSe...

SQL 2008 Service Pack 1 RTM now available

sqldbatips.com blog — Wed, 08 Apr 2009 18:27:57 GMT

Service Pack 1 for SQL Sevrer 2008 is now available (download link below). Two of the key features in

SQL 2008 Service Pack 1 RTM now available

jl999 — Thu, 09 Apr 2009 01:16:08 GMT

I just followed the steps outlined in this article, plus the "Slipstream a SQL Server Update" in the SP1 setup helpfile, and successfully installed SQL 2008 + SP1. Thanks!

In the help file, it has a step to copy sqlsupport.msi file from each architecture. But this blog post doesn't have it. Do we still need it? I followed help file and copied the msi files.

re: Creating a merged (slipstreamed) drop containing SQL Server 2008 RTM + Service Pack 1

petersad — Thu, 09 Apr 2009 02:13:44 GMT

You don't need to copy the sqlsupport.MSI over.

Slipstreaming SQL Server Installations and the SP1 Controversy

Carpe Datum — Thu, 09 Apr 2009 18:30:35 GMT

Yesterday, along with several hundred other folks, I told you that SQL Server 2008 Service Pack 1 was

SQL Server 2008 SP1 and Cumulative Updates Explained.....

CSS SQL Server Engineers — Thu, 09 Apr 2009 19:51:34 GMT

One of our readers sent me the following questions I think you will find valuable when understanding

SQL Server 2008 SP1 + CU1 or CU4 or what ?

Developer hearted / Relational minded — Sat, 11 Apr 2009 10:58:48 GMT

I saw some confusion around the availability of SP1 and CU4 on the web, therefore decided to put on a

Rolling upgrade of 1 instance from 2-node, 2-instance sql failover cluster to slipstreamed sql 2008 SP1

Esoteric — Sat, 11 Apr 2009 15:00:57 GMT

Now that SQL Server 2008 SP1 is released (download link here ), it is time to test a very interesting

MS SQL Server 2008 Service Pack 1 (SP1)

Ansichtssachen — Sun, 12 Apr 2009 18:35:33 GMT

Das 1. Service Pack für den Microsoft SQL Server 2008 ist erschienen und kann heruntergeladen werden. Mit diesem SP1 kann man sich auch eine neue Installations-CD/DVD bauen, die es einem ermöglicht, bei einer Neuinstallation alles in einem Rutsch zu inst

re: Creating a merged (slipstreamed) drop containing SQL Server 2008 RTM + Service Pack 1

wleong — Mon, 13 Apr 2009 20:45:40 GMT

It seems with steps 3, 4 and 5 that you practically end up with a duplicate set of SP1 files at the end of slipstream preparation -- one in SQLServer2008_FullSP1 and one in PCU. Did I read that correctly?

Create a merged (slipstream) drop containing SQL Server 2008, Server Pack 1 and a Cumulative Update (CU) based on Server Pack 1

SQL Server Setup — Thu, 16 Apr 2009 05:27:48 GMT

Today, I am going to show you how to create new source media that will slipstream the original source

re: Creating a merged (slipstreamed) drop containing SQL Server 2008 RTM + Service Pack 1

Fraggel — Fri, 17 Apr 2009 10:16:54 GMT

The "SQL Server features discovery report" says verion 10.1.2531.0, but the serverproperty('ProductVersion') returns 10.0.2531.0! The 'ProductLevel' server property returns SP1

SQL Server 2008 SP1

SQL Server — Sat, 18 Apr 2009 03:35:28 GMT

El primer service pack para SQL 2008 ya está disponible, puedes bajarlo desde la siguiente dirección

SQL Server 2008 SP1

Noticias — Sat, 18 Apr 2009 03:35:39 GMT

El primer service pack para SQL 2008 ya está disponible, puedes bajarlo desde la siguiente dirección

SQL Server 2008 Slipstream Frequently Asked Questions

SQL Server Setup — Sun, 26 Apr 2009 01:15:16 GMT

General slipstreaming questions: Question #1: What is Slipstreaming? Answer: It is a term used to describe

re: Creating a merged (slipstreamed) drop containing SQL Server 2008 RTM + Service Pack 1

Paul Hickman — Thu, 30 Apr 2009 17:19:15 GMT

After following these instructions, the installation will no longer work if the current working folder is not the folder that contains setup.exe as the relative path ".\PCU" is invalid.

You may need to adjust scripted installs to cater for this.

re: Creating a merged (slipstreamed) drop containing SQL Server 2008 RTM + Service Pack 1

petersad — Fri, 01 May 2009 10:38:29 GMT

Yes you are correct regarding the relative path. I actually noticed this the other day myself. Anyways I have clarified the instructions that the full patch is needed as the relative path may not always work.

re: Creating a merged (slipstreamed) drop containing SQL Server 2008 RTM + Service Pack 1

danjamSQL — Sun, 03 May 2009 03:50:44 GMT

I wish I could create a slipstreamed DVD to install from. However, unless the DVD is in drive D: on every computer, then the

PCUSOURCE="{Full path}\PCU"

requirement is troublesome.

re: Creating a merged (slipstreamed) drop containing SQL Server 2008 RTM + Service Pack 1

danjamSQL — Sun, 03 May 2009 03:52:03 GMT

For this step:

5. Copy all files not the folders, except the Microsoft.SQL.Chainer.PackageData.dll, in c:\SQLServer2008_FullSP1\PCU\<architecture> to C:\SQLServer2008_FullSP1 \<architecture> to update the original files.

is it possible to move the files instead so that they are not taking up double space on our file server?

re: Creating a merged (slipstreamed) drop containing SQL Server 2008 RTM + Service Pack 1

petersad — Sun, 03 May 2009 04:58:01 GMT

Regarding the last 2 comments:

1) PCUSource comment: initially I documented PCUSource=.\PCU but if you current folder is not the same as the location to setup.exe, the PCUSource folder could not be located since the command parameter does not support a relative path. However, if you plan to burn a DVD, .\PCU might just work for you but I have not tried it. We need to fix the PCUSource, so it can support a relative path but the timeline is unknown.

2)"Moves the files" instead: No you can move all of the files in PCUSource location.

re: Creating a merged (slipstreamed) drop containing SQL Server 2008 RTM + Service Pack 1

Number2 — Fri, 08 May 2009 08:41:20 GMT

So, just for clarification...

Step 7 says to run setup as you normally would...now, are you saying that no matter what I chose for my setup options, once it starts the setup, it will actually slipstream the bytes from those PCU folders into the rest of the media? Do the choices of installation options determine how much of the media gets slipstreamed?

Or does all of this really only amount to the setup routine running the RTM setup and then running of SP1 right after?

re: Creating a merged (slipstreamed) drop containing SQL Server 2008 RTM + Service Pack 1

petersad — Fri, 08 May 2009 09:02:39 GMT

Slipstream merges the original files with the update to perform a "single" install. Only the files that need to be merged will be merged.

re: Creating a merged (slipstreamed) drop containing SQL Server 2008 RTM + Service Pack 1

Number2 — Fri, 08 May 2009 22:44:05 GMT

Is it possible to slipstream CU1 into this as well?

re: Creating a merged (slipstreamed) drop containing SQL Server 2008 RTM + Service Pack 1

petersad — Sat, 09 May 2009 06:16:00 GMT

See http://blogs.msdn.com/petersad/archive/2009/04/16/create-a-merged-slipstream-drop-containing-sql-server-2008-server-pack-1-and-a-cumulative-update-cu-based-on-server-pack-1.aspx.

You can not slipstream RTM + CU.

re: Creating a merged (slipstreamed) drop containing SQL Server 2008 RTM + Service Pack 1

trer — Mon, 11 May 2009 15:14:47 GMT

This slipstream functionality is very nice - but - isn't there any way to avoid using an absolute path to the PCU folder?

When you have several distinct networks & DMZ/FMIs with different installmedia-servers, we will need to create distinct defaultsetup.ini's for each location if the PCUSOURCE must be an absolute path. If a releative path was used, we could just create one and automatically push it to each install-media server.

re: Creating a merged (slipstreamed) drop containing SQL Server 2008 RTM + Service Pack 1

petersad — Mon, 11 May 2009 16:55:31 GMT

See question #11 at http://blogs.msdn.com/petersad/archive/2009/04/24/sql-server-2008-slipstream-frequently-asked-questions.aspx if you would like to use a relative path.

Installing SQL Server Express on Windows 7 Release Candidate

SQL Server Express WebLog — Thu, 14 May 2009 21:49:13 GMT

When installing SQL Server 2005 RTM/SP1/SP2 and SQL Server 2008 RTM on Windows 7 RC it presents you with

Windows 7 RC 版でのVisual Studio 開発環境とSQL Server

ディベロッパー製品開発統括部 Blog — Thu, 21 May 2009 12:20:37 GMT

Visual Studio 2010 英語版プレリリースの提供が今週から開始されました。 ( VS2010 プレリリース英語版ページ ) 我々開発チームも開発の最終段階に入った Visual Studio

re: Creating a merged (slipstreamed) drop containing SQL Server 2008 RTM + Service Pack 1

Prithvy — Sat, 23 May 2009 09:49:56 GMT

is it possible slipstream Sql 2005 SP3 ..?

re: Creating a merged (slipstreamed) drop containing SQL Server 2008 RTM + Service Pack 1

petersad — Sat, 23 May 2009 17:09:32 GMT

No, it is not possible to Slipstream SQL 2005 SP3

Takes a lot of space.

LinoX — Wed, 24 Jun 2009 16:12:25 GMT

Is there a way to reduce the size of the setup?

With slipstreamed setup we have to include both the original files and the SP1 files.

Distributing an old file (because during the setup gets replaced by the service pack) is a waste of resources.

I need a setup that installs directly SP1 (as the result of the slipstreamed setup) but takes less space.

I need something like

"Microsoft SQL Server 2008 Express with Advanced Services with Service Pack 1".

Any hits on how to build it?

(actually on microsoft site such download is not present)

re: Creating a merged (slipstreamed) drop containing SQL Server 2008 RTM + Service Pack 1

Selvakumar.r2 — Wed, 12 Aug 2009 17:18:10 GMT

I tried this slipstream setup in Windows 7. It is successfully installed, but the problem is after installing the sql server, the msi installer is not closed it's transaction. It is difficult to install other softwares,the msiexec is not terminated. I can't uninstall or install any software due to this process. when i tried to install or uninstall any software, i am getting the error message that "another installation is in progress. complete that installation before proceeding with this install"

re: Creating a merged (slipstreamed) drop containing SQL Server 2008 RTM + Service Pack 1

petersad — Wed, 12 Aug 2009 19:45:03 GMT

Likely it is not the slipstream process causing this. Possibly another installation was kicked off, maybe through Windows Update. After waiting a long time (an hour or so) and the process is still running, you can just kill the MSIEXEC process.