Creating a SQL Server 2008 Management Studio Express Slipstream drop

[Updated on 2/16/2010: Corrected an issue with step #6]

In today’s blog I will show you have to create a drop of SQL Server 2008 Management Studio Express with Service Pack 1. Without these steps, you need to install the original release of Management Studio Express and then apply Service Pack 1. Once you run these steps, you can now install the original release of Management Studio Express and SP1 together.

These steps minimize an increase in package size. There are ways for you package up this drop for distribution, but I’m not going to cover these steps at this point in time.

These instructions are specifically for the x86 package, but could work for x64. I just have not worked through the exact steps.

These steps create a folder called merge, which contains Management Studio Express with Service Pack 1.


1. Download & Save (don’t RUN) the x86 SQL Server 2008 Management Studio Express (SQLManagementStudio_x86_ENU.exe) package from here.

2. Download & Save (don’t RUN) the x86 SQL Server 2008 Service Pack 1 (SQLServer2008SP1-KB968369-x86-ENU.exe) package from here.

3. Extract the packages as follows:

SQLManagementStudio_x86_ENU.exe /x:c:\temp\rtm

SQLServer2008SP1-KB968369-x86-ENU.exe /x:c:\temp\sp1

4. Run this Robocopy command to create the merged drop

robocopy c:\temp\rtm c:\temp\merge /s

5. Run these commands to copy files from the SP1 drop to the original media folder

robocopy C:\temp\sp1\x86 C:\temp\merge\x86 /XF Microsoft.SQL.Chainer.PackageData.dll

robocopy C:\temp\sp1 C:\temp\merge Setup.exe

robocopy C:\temp\sp1 C:\temp\merge Setup.rll

6. Run these commands to create an optimized SP1 folder

robocopy C:\temp\sp1 c:\temp\merge\pcu mediainfo.xml

robocopy C:\temp\sp1\x86 c:\temp\merge\pcu\x86 microsoft.sql.chainer.packagedata.dll

robocopy C:\temp\sp1\x86\Setup c:\temp\merge\pcu\x86\Setup sql_ssms.msp

robocopy C:\temp\sp1\x86\Setup\1033 c:\temp\merge\pcu\x86\Setup\1033 sql_ssms_loc.msp

robocopy C:\temp\sp1\x86\Setup\1033 c:\temp\merge\pcu\x86\Setup\1033 sqlsupport.msi

robocopy C:\temp\sp1\x86\Setup\sql_common_core_msi c:\temp\merge\pcu\x86\Setup\sql_common_core_msi sql_common_core.msp

robocopy C:\temp\sp1\x86\Setup\x64 c:\temp\merge\pcu\x86\Setup\x64 /S

robocopy C:\temp\sp1\x86\Setup\x86 c:\temp\merge\pcu\x86\Setup\x86 /S

robocopy C:\temp\sp1\x86\setup\1033\pfiles C:\temp\merge\pcu\x86\Setup\1033\pfiles /s

robocopy C:\temp\sp1\x86\setup\1033\windows C:\temp\merge\pcu\x86\Setup\1033\windows /s

7. Create a defaultsetup.ini file to tell Setup where to find the Service Pack

echo [SQLSERVER2008]  > C:\temp\merge\x86\defaultSetup.ini

echo PCUSOURCE=".\PCU"  >> C:\temp\merge\x86\defaultSetup.ini

8. Additional notes:

a. You no longer need the c:\temp\rtm and c:\temp\sp1 folders

b. You should verify the installation works as expect, run setup.exe in the \merge folder

c. You can package up the merge folder for distribution

Comments (4)

  1. I have put together steps for you to build an Express Management Studio with Service Pack 1.  See

  2. apostle says:

    i followed the instructions exactly 3 times for good measure and keep getting the same error:

    TITLE: Microsoft SQL Server 2008 Setup


    The following error has occurred:

    Error reading from file: C:tempmergePCUx86Setup1033PFilesSqlServr100SetupReleasex86AddNode.xml.   Verify that the file exists and that you can access it.

    i don’t know what is referencing this strange path that doesn’t even exist.

  3. BoxingSurfer says:

    A total waste of time

    I followed this procedure three times.

    It doesnt work. As Apostle said above, the resulting slipstream contains references to paths that dont exist in the package.

    You should take this post down to save others  from wasting their time also

    better luck next time.

  4. petersad says:

    I have fixed the issue you mentioned above by adding two copying steps to step #6. Let me know if you have any future issues.