June 24, 2004 at 8:02 am
When I do the following query I get these results:
SELECT @@VERSION
Output:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 2)
How can I determine if this is SP3 or SP3A????
June 24, 2004 at 9:05 pm
Version Number | Service Pack |
8.00.194 | Microsoft SQL Server 2000 |
8.00.384 | Microsoft SQL Server 2000 SP1 |
8.00.532 | Microsoft SQL Server 2000 SP2 |
8.00.760 | Microsoft SQL Server 2000 SP3 |
8.00.818 | Microsoft SQL Server 2000 SP3 w/ Cumulative Patch MS03-031 |
Derrick Leggett
Mean Old DBA
When life gives you a lemon, fire the DBA.
June 25, 2004 at 12:29 am
mmm Microsoft must have forgotten to increase the build number for SP3a, despite some of the added fixes, SP3 and SP3a report the same version (8.00.760). The only way to tell is by checking a number of .DLL's on the hard disk.
Release | Sqlservr.exe |
---|---|
RTM | 2000.80.194.0 |
SQL Server 2000 SP1 | 2000.80.384.0 |
SQL Server 2000 SP2 | 2000.80.534.0 |
SQL Server 2000 SP3 | 2000.80.760.0 |
SQL Server 2000 SP3a | 2000.80.760.0 |
To determine whether you have SP3 or SP3a installed, look at the version number of the Net-Library file, Ssnetlib.dll. If the version number of this file is 2000.80.760.0, you have SP3; if the version number of this file is 2000.80.766.0, you have SP3a.
Assuming that an instance was installed using the default settings, you can find the Ssnetlib.dll file in one of these locations:
To find out whether you have the SP3 or SP3a setup folders, open the SP3Readme.htm file and read the first page. The service pack version, SP3a or SP3, is listed at the top of the first page.
Julian Kuiters
juliankuiters.id.au
June 25, 2004 at 4:21 am
All most helpfull !!!
Thank you
August 11, 2004 at 4:57 am
One of the things I read when SP3a first come out was that is was released due to the installation process failing when applying normal SP3 on Windows 2003 Server. Hence SP3a was released to overcome the deployment on Windows 2003 Server.
My understanding was the contents were effectively the same, however as shown in previous post there was one file difference and a registry entry showing a different build.
Therefore, unless your SQL2K is running on Windows 2003 Server, if it reports SP3 all would be good!
Robert
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply