[There's a reason that Yoda is the unofficial mascot of SBS. Size indeed matters not.] Patching this month SBS 2003 sp2 standard - THE OFFICIAL BLOG OF THE SBS "DIVA"
Thu, Jul 17 2008 0:17 bradley

Patching this month SBS 2003 sp2 standard

Let's review again.

1.  On servers turn off auto updates (But Susan?  You the patchaholic telling us to turn off auto updates?)  On a server you bet your little bippie.  I want to patch on MY schedule not Microsoft's.  This month I'm even taking the precaution of manually using Microsoft Update and not Shavlik because I want to ensure the right patches come down.

2.  Again, I'll say it before, I'll say it again.  Do the SQL patches one at a time.  Untick everything else and just bring down one, then another. 

I patched SBS Monitoring, SharePoint and WSUS instances on this box.  I have no BackupExec, or ISA on this particular box.  Be careful with LOB apps that use SQL you may need to know (or reset) the SA password.

When I look in the services I have SBS Monitoring on MSDE, SharePoint on WMSDE and WSUS on Windows Internal Database (WSUS 3 sp1)

How to identify your SQL Server version and edition:
http://support.microsoft.com/kb/321185/

First up let's confirm what SBS Monitoring file version is:

 On a bog standard SBS 2003 box, go to C:\Program Files\Microsoft SQL Server\MSSQL$SBSMONITORING\Binn

Find the sqlserver.exe file, right mouse click and look at the properties:

2000.080.2050.00 Hotfix 2273

Next SBS SharePoint on WMSDE

C:\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\Binn

2000.080.2050.00 Hotfix 2273

Now you are going to love this.. I couldn't figure out where on the server the Windows Internal Database was located so I did the trick of looking at the properties of the Services.

Look under Windows Internal Database,

C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Binn\sqlservr.exe -sMICROSOFT##SSEE

 

AH HA there it is, remember look for that BINN folder

And this time we have a different number because it's on the 2005 series of SQL Server

2005.090.3068.00

 This grid helps a bit to narrow it down as to what we use to have and what ranges we should expect to be patching from.

Generally speaking most of us are on the GDR branch

So for MSDEs (SBS Monitoring), WMSDE (SharePoint on Standard) you will be patching from build version .2039 and patching it up to .2050

For Windows Internal Database (WSUS) you will be patching from .3042 to build .3068

But if you want to manually confirm that all your SQLs are SQLing as they should be, there's an overview of how to tell what build they are on.

Filed under:

# re: Patching this month SBS 2003 sp2 standard

Monday, July 21, 2008 7:00 PM by Dean

Could you back up a little bit and explain how you even got on this topic ? What triggered it ? Then could you explain what the difference is between a "build" number and a "version" number ? In all the screen shots you highlight version numbers but in the article you talk about build numbers. They don't seem to match up number wise.

# re: Patching this month SBS 2003 sp2 standard

Tuesday, July 22, 2008 9:05 AM by bradley

Build and Version numbers are indentifying the same thing.  The last part of the File Version has 90.3068.00... that 9.00.3068 is what SQL refers to as the build number.

Patch Tuesday triggered it.

And if you want to see how to confirm that all of your SQL instances are patched manually per your eyeballs, that's how to do it.

# re: Patching this month SBS 2003 sp2 standard

Tuesday, July 22, 2008 11:42 AM by Dean

OK then why do the version/build numbers read as 090.3068.00 and in the KB chart they read as 9.00.3042 ? Should there not be some consistency here ? I mean 090 is different from 9