This method does not work and the error message is that there is no instance of SQL server to be updated.

thank you for the Information!

Instructions for slipstreaming the installation can be found at http://msdn.microsoft.com/en-us/library/dd638062.aspx#Slipstream

By using the Slipstream method, I was able to install both the server and the service patch at the same time, without uninstalling MSXML 6 SP2. There are a couple of issues that could trip someone up, though. To the posting referenced above, I add the following notes:

If there was a prior installation of SQL Server 2008 that included Reporting services, the installation may fail, returning the message, “The Reporting Services catalog database file exists. Select a Reporting Services files-only mode installation.” If that happens, setting the reporting services installation mode to “Files Only”, using the parameter settting, RSINSTALLMODE=”FilesOnlyMode”, will allow the installation to proceed.

As of May 29, 2009 (when this was written) there were no cumulative updates to SQL Server 2008 — there is only Service Pack 1. So, step 4 in the procedure under the heading “Slipstream a SQL Server Update / Overview”, can be skipped. With a proper configuration file, the entire installation can be done hands-free, by issuing the following two commands in the Command Prompt window, or in a batch file:

en_sql_server_2008_sp1_x86 /QS=”True”

D:\SETUP /CONFIGURATIONFILE=”InstallSqlServr2008Config.ini”

while en_sql_server_2008_sp1_x86.exe is in the current working directory.

Note that the service pack installer is run BEFORE the SQL Server installer. This loads the support files, and enables the slipstream method of installation.

Replace D: with the actual drive letter of the DVD drive containing the SQL Server 2008 Setup disk.

The flag /QS=”True” causes the service pack to install without prompting the user — avoids having to answer the “Do you accept the terms of the EULA” and such. The “/Action” parameter is NOT valid for the service pack installation, and will cause the installation to terminate with an error, if included. It may be included for the SQL Server main installation, either on the command line or within the configuration file.

Yes, the whole “installing experience” is so fantastic and extremely robust! What a nice peace of software … *plonk*