Partilhar via

Welcome to SQL Server 2008 Patching

  • Artigo

We have posted the first cumulative update for SQL Server 2008 aptly named Cumulative Update 1 (CU1). I thought before you considered installing a patch for SQL Server 2008, you would like to see a tour of what it looks like compared to SQL Server 2005 patch installations.

The first thing I did was download the package for the update from the following KB article:

https://support.microsoft.com/kb/956717

This article includes a list of fixes contained in CU1.

If you remember, I wrote a blog post back in April on how you can download your own fixes from KB articles as seen from this screen shot of the article on the web:

image

Once I received my email containing the hotfix download instructions, I downloaded the fix to the local drive where I had SQL Server 2008 installed. I then uncompressed the zip file, and ran the package (which for x64 is called SQLServer2008-KB956717-x64.exe).

Let's take a look at this journey of patching through a series of screen shots.

When I run the executable I am first presented with some setup rule checks to catch problems before I try to install. Notice how the screens look very similar to the user experience of the standard SQL Server 2008 setup you run from the DVD.

image

Next I need to respond to a licensing agreement (We've caught the wording mistake at the top. It shouldn't say "Service Pack").

image

Now you get to pick which instances to update (which in my case is only the default instance). image

Notice the Version Information at the bottom right of the screen. It shows you information such as:

Edition: Enterprise, Standard, ...

Patch Level: This is the version installed for this instance (10.0.1600.22 is RTM). If you had already applied a patch, you can see that here in the version (for example, CU1 is 10.0.1763)

Architecture: x64, x86, ia64

Service Pack: This eventually will be the service pack level (1, 2, ...) if installed

Upgrade Status: Not installed means this patch has not been installed yet. Installed would mean you have already applied the patch you are trying to install.

Hit Next and you get to confirm your selection

 image

Select Patch and off you go with the update for CU1. When it is complete you will get a screen like this:

image

Hit Next and you see the final screen for the update.

image

Notice at the top a link to a Summary log file. This is the same type of Summary log file you get for the standard installation of SQL Server 2008. If you had problems you would see that failure on this screen and use the Summary log file to determine the problem. You may also notice that this link points to c:\program files\microsoft sql server\100\setup bootstrap\log which is the same directory where the standard setup program stores log files.

If you click this link you can see from the Summary log file fragment I've included that this setup was run to "Patch":

Overall summary:   Final result:                  Passed   Exit code (Decimal):           0   Exit message:                  Passed   Start time:                    2008-09-25 13:10:17   End time:                      2008-09-25 13:24:37   Requested action:              Patch

Instance MSSQLSERVER overall summary:   Final result:                  Passed   Exit code (Decimal):           0   Exit message:                  Passed   Start time:                    2008-09-25 13:19:09   End time:                      2008-09-25 13:24:26   Requested action:              Patch

Any way to avoid these screens?

Just like the hotfix installer for SQL Server 2005, there is a way to run a 2008 hotfix package without having to respond to the screens. The basic syntax look like this:

<package.exe> /QUIET /INSTANCENAME=<instance>

or

<package.exe> /QUIET /ALLINSTANCES

So for the x64 update, I ran this for my default instance:

SQLServer2008-KB956717-x64.exe /QUIET /INSTANCENAME=MSSQLSERVER

A separate console window will be launched like the following:

image

When the patch is complete this window is closed. You can check the summary log files to see if the patch was successful. You can also get more details on the progress if you use the /INDICATEPROGRESS option, but be warned it dumps a bunch of output to this console window.

What about Uninstall?

Just like the SQL Server 2005 hotfix installer, you can uninstall SQL Server 2008 patches.  Here is a screen shot of "Program and Features" on my Windows 2008 Server machine after I selected "Installed Updates"

image

So I picked "Hotfix 1763 for SQL Server 2008..." and selected Uninstall from the menu above all the updates (you can also right-click and select Uninstall).

The screens look very similar to the process of installation...

image

image

image

image

image 

The uninstall of CU1 does something very interesting when it is done. It does not remove the updates to the SQL Server 2008 Setup Support Files. You will notice in this screen shot the version of SQL Server 2008 Setup Support Files is 10.0.1763 after I've uninstall the CU1 patch.

image

This allows you to take advantage of setup fixes we included in CU1 should you decide to use setup in the future to add instances or features.

How does this work? Well, read my next blog post where I will show you how we have devised a method to fix setup before you actually run setup (trust me it will make sense when you read the blog post).

 

Bob Ward
Microsoft

logo-header-sql08-dg

Comments

  • Anonymous
    September 26, 2008
    PingBack from http://www.easycoded.com/welcome-to-sql-server-2008-patching/

  • Anonymous
    September 26, 2008
    We have posted the first cumulative update for SQL Server 2008 aptly named Cumulative Update 1 (CU1)

  • Anonymous
    September 26, 2008
    You've been kicked (a good thing) - Trackback from DotNetKicks.com

  • Anonymous
    September 26, 2008
    http://weblogs.asp.net/markwisecarver/archive/2008/09/26/welcome-to-sql-server-2008-patching.aspx

  • Anonymous
    September 29, 2008
    When i try to install CU1 on a 2-node cluster it fails because it extracts the setup routines into a temporary folder on one of the shared cluster drives (the I: drive in my case) and then part way through the CU install it takes this cluster drive offline, causing the install to fail with error: The directory 'i:2ebc5d3c7f9e01eff86a7b9489c78c' doesn't exist. Any idea if there is a workaround to this?

  • Anonymous
    September 30, 2008
    The comment has been removed

  • Anonymous
    October 05, 2008
    Hi geoff2, I've experienced same problem. You can solve it by running installation at passive node. I've reported this issue to Microsoft https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=371993 You are welcome to vote.

  • Anonymous
    November 07, 2008
    Ya tenemos disponible el primer CU para SQL Server 2008 que corrige algunos bugs como el reportado por

  • Anonymous
    November 12, 2008
    Bob Ward has posted a very thorough walk-through of the CU1 installation process. He talks about some

  • Anonymous
    March 27, 2011
    In 4th figure above, the edition is enterprise. Mine is win7 ulimate and 64 bit. 2 gb ram. Installed vs 2010 and not yet installed sql server 2008(developer). Where can i get the service pack for developer edition. I installed one service pack 2 for sql server but the edition is : express :-( can some one guide me to get the service pack for developer. Mail me to formulaone87@gmail.com ...PLZ HELP