In this tutorial we will discuss an overview of SQL Server servicing installation. It is possible to upgrade any installed SQL Server 2008 component with a SQL Server 2008 servicing update. In this case, if the version of the component is later than the version update available then the Setup program will not update it.

Take into consideration the following when you install SQL Server 2008 updates:

All the features that belong to an instance of SQL Server have to be updated together. For instance, if you update the Database Engine, you have to update Analysis and Reporting Service components if they are installed as part of the same instance of SQL Server. If the features are shared, like Management Tools, Business Intelligence Development Studio, or SQL Server Integration Services then they must always have the most recent update. Let’s say a component or instance in the feature tree is not selected, the component or instance then will not be updated.

SQL Server 2008 update log files are saved, by default to %Program Files%\Microsoft SQL Server\100\Setup Bootstrap\LOG\.

With Service Pack 1 (SP1), you are allowed to slipstream an update with the initial media to run the initial media update at the same time.

Back-up all data before you apply a SQL Server 2008 update

Updates are conveniently accessible through Microsoft update. I would scan for updates regularly.

Disk Space Requirements

A good rule of thumb would be to allocate about 2.5x the size of the package to install, download, extract the package

The approximate sizes of the SP1 packages are:

X86: 270MB, X64: 331MB, Ia64: 320MB

This overview will discuss three options to slipstream an update in the SQL Server 2008 installation; Install the most recent update with the original release version of SQL Server 2008 setup directly, Slipstream express Core Service pack along with cumulative update, update the initial media files.

To slipstream updates, patches or service packs actually means to integrate them into the installation files of their original software, so that the resulting files will allow a direct installation of the updated software.

Before We Start

Important! Before you install SQL Server updates back up you system databases. Most importantly the master, msdb, and model databases because the update changes these databases, conflicting them with earlier versions of SQL Server 2008. Also Backups are necessary if you want to reinstall SQL Server minus the updates. Additionally, it is prudent to back up your user databases.

It is vital that when you apply updates to instances of SQL Server that are engaged in a replication topology, that you also backup the replicated together with your system databases beforehand.

Remember to back up your Analysis Services databases, configuration file, and repository which are located:

Default Location for the installed Analysis Services databases:

C:\Program Files\Microsoft SQL Server\MSAS10\\OLAP\Data\

Default Location for the Analysis Services configuration setting in the msmdsrv.ini configuration file:

C:\Program Files\Microsoft SQL Server\MSAS10\\OLAP\Config\ directory

Databases that contain the Analysis Services repository, are only required if Analysis Services was configured to work with the Decision Support Objects (DSO) library.

The Analysis Services database, configuration file, and repository will be thrown back to an earlier version if not backed-up.

Verify that the system databases have enough free space. There is at least 500KB of free space, iIf the autogrow option is not selected for the master and msdb system databases. To check and see if there is at least 500KB free, run the sp_spaceused system stored procedure on the master and msdb databases.

STOP ALL Services and Applications! This allows you to avoid a possible restart of the system. (Services cannot be stopped in a failover cluster environment)

Slipstreaming is integrating a SQL Server 2008 update and the original installation media so that the initial media and the update are installed at the same time. This way when you run the first version of SQL Server 2008 Setup, it copies it to the local computer, and then re-runs from the local copy. If there happens to be a later version for setup on the pc, then the setup program runs the updated setup. Slipstream is supported with the initial media and service pack, or with the initial media, service pack, and cumulative update.

Here are a couple different options of how you can slipstream an update:

Install the latest update with the original release version of SQL Server 2008 Setup directly, Slipstream Express Core Service Pack with cumulative update or Update the original media files.

We suggest if you are running on only a couple computers then use this option:

Install the latest update with the original release version of SQL Server 2008 Setup directly.

To begin, you must first install the following required for SQL Server 2008

Microsoft Windows Installer 4.5, Microsoft .NET Framework 3.5 Service Pack 1 (except on IA-64 platform where the .NET Framework is not supported, and the .NET Framework 2.0 SP2 is required).

Download the service package and cumulative updates that you want to slipstream. Then select the language or architecture package to work with. Service packages MUST math both languages and architecture; cumulative updates are language-neutral.

Now double-click the service pack to install SQL Server 2008 Setup support files. Afterwards, search the “SQL Server 2008 Setup Support Files” to double-check that the updated setup installed correctly. You can find the support files by navigating the control panel and using the “Add or remove Programs” item.

Then for each package, extract the contents of the package by running this script with the command prompt:

.exe /x:\

The name of the package is in the form:

PCU: SQLServer2008SP1-.exe

CU: SQLServer2008SP1-.exe

The architecture placeholder represents the different hardware platforms. For example, it can represent one of the following folders:

x86

x64

IA64

For example, run the following commands to extract the contents of the PCU package:

SQLServer2008- KB123456-IA64.exe /x:c:\MyUpdate\PCU

SQLServer2008- KB123456-x64.exe /x:c:\MyUpdate\PCU

SQLServer2008- KB123456-x86.exe /x:c:\MyUpdate\PCU

If you want to include a CU based on the PCU, extract out the CU packages to c:\MyUpdate\CU

Start the SQL Server 2008 Setup program specific the path for the service pack and cumulative update by using the /PCUSource and /CUSource parameters

For instance here is a path based on the extracted location:

Setup.exe /PCUSource = c:\MyUpdate\PCU /CUSource= c:\MyUpdate\CU

Just in case you are slipstreaming SQL Server in WOW64, you may need to do one of the following:

It is also possible to skip the installation center, and specify the /Action parameter and the /x86 parameter on the command line.

Or, on the Options page of the Installation Center, select x86.

Here is another option. We suggest this option if you are running the upgrade on a couple computers:

Slipstream Express Core Service pack along with cumulative update

Microsoft Windows Installer 4.5, Microsoft .NET Framework 3.5 Service Pack 1 (SQL Server Express only requires .NET 2.0 SP2, however the version is not public available, so you will need to install .NET 3.5 SP1

Download the SQL Server Express core package and cumulative update that you want to slipstream. Then select the language or architecture of SQL Server Express that matches your environment. These cumulative updates are language-neutral.

Then extract all the contents by running the following scripts at the command prompt:

.exe /x:\

The name of the package is in the form:

CU: SQLServer2008-.exe

The architecture placeholder represents the different hardware platforms. For example, it can represent one of the following folders:

x86

x64

IA64

For example, run the following commands to extract the contents of the cumulative update package:

SQLServer2008-KB123456-IA64.exe /x:c:\MyUpdate\CU

SQLServer2008-KB123456-x64.exe /x:c:\MyUpdate\CU

SQLServer2008-KB123456-x86.exe /x:c:\MyUpdate\CU

Now start the SQL Server 2008 Setup program and determine the path for the cumulative update files and service pack by using /CUSource parameters.

Update the initial media files:

We suggest that you use this option if you are running a patched setup on many computers or large deployments, or for when an administrator wants to make this accessible to users. I would strongly suggest that you test before you make it available to users. Here is a couple different angles:

Download the correct service pack and the optional cumulative update based on the specific service pack you wish to use to update the initial media files. Now you must download the service pack and updates for every platform, simply because the initial media contained the files for each. To clarify, you need either the three packages downloaded for merging the initial media and a service pack or six packages for merging the initial media, service pack, and cumulative update.

Again for each package, extract the contents of the package by running the following script at eth command prompt:

.exe /x:\

The name of the package is in the form:

PCU: SQLServer2008SP1-.exe

CU: SQLServer2008SP1-.exe

The architecture placeholder represents the different hardware platforms. For example, it can represent one of the following folders:

x86

x64

IA64

For example, run the following commands to extract the contents of the PCU package:

SQLServer2008- KB123456-IA64.exe /x:c:\MyUpdate\PCU

SQLServer2008- KB123456-x64.exe /x:c:\MyUpdate\PCU

SQLServer2008- KB123456-x86.exe /x:c:\MyUpdate\PCU

The previous command merges the three architectures into a single folder. If you want to include a CU based on the PCU, extract the cumulative update packages out to c:\MyUpdate\CU

Now copy the contents of the SQL Server 2008 DVD to a local folder. In order to update the initial media, just copy the SQLSupport.msi file from C:\MyUpdate\PCU\\setup\\sqlsupport.msi to C:\SQLServer2008RTM\\Setup\sqlsupport.msi. Ensure that you copy Sqlsupport.msi for each architecture.

**If you are slipstreaming to integrate a cumulative update package also, use the files in the extracted cumulative update folder in place of.

Then copy the setup.exe and setup.rll files from C:\MyUpdate\PCU\ folder to the root folder that contains the source media from the DVD.
**If you are slipstreaming to integrate a cumulative update package also, use the files in the extracted cumulative update folder in place of.

Now in order to update the files in the initial installation media, copy all files (not the folders) except Microsoft.SQL.Chainer.PackageData.dll in c:\MyUpdate\PCU\ to c:\SQLServer2008RTM\

**If you are slipstreaming to integrate a cumulative update package also, use the files in the extracted cumulative update folder in place of.

Finally, start the Setup.exe program that is located at C:\SQLServer2008RTM and specify the values for /PCUSource and /CUSource parameters. For instance, C:\SQLServer2008RTM\Setup.exe /PCUSource=c:\MyUpdate\PCU /CUSource= c:\MyUpdate\CU.

We suggest if you place the folder on a share for user installs, to set the /PCUSource and /CUSource parameters to a UNC path (Universal Naming Convention)

When the setup is finished whether you nee dto restart the computer or not, afterwards it is ok to turn on any services that you stopped before you applied the update.

For good practice, you might also want to make another backup of the upgraded master, msdb, and model databases immediately after successful installation.

Uninstalling updates to SQL Server 2008

From the “Programs and Features” section within the Control Panel, you can uninstall SQL Server 2008 cumulative updates. This is possible because each cumulative update is listed separately. The most efficient way to do an uninstall is to start with the latest update or service pack applied to the instance of SQL Server and work backwards from it.