Build numbers

I am trying to restore a master database after a server rebuild and need to get the build number back to 8.00.818. I have installed (or so I thought) the SP3a and the 8-11-03 patch to get it to that build number but when I check the build number in Enterprise Manager it still shows 8.00.194. Help?How are you getting the build number from Enterprise Manager? You should
connect to your SQL Server using Query Analyzer and run the following
command to get the SQL Server's build number:
SELECT @.@.VERSION
GO
May be you haven't installed the service pack on the client machines.
This might be helpful: http://vyaskn.tripod.com/sqlsps.htm
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Chad" <anonymous@.discussions.microsoft.com> wrote in message
news:819D85D5-070C-4150-87FB-B9A0C5A2B2FB@.microsoft.com...
I am trying to restore a master database after a server rebuild and need to
get the build number back to 8.00.818. I have installed (or so I thought)
the SP3a and the 8-11-03 patch to get it to that build number but when I
check the build number in Enterprise Manager it still shows 8.00.194. Help?|||I have done that as well to get the build number but under properties of the sql instance name is where I was getting the information from Enterprise Manager (is that wrong?). And after applying SP3a and the 8-11-03 patch it hasn't changed the build information. I have taken the defaults for installation of the SP and patch. I Have completely rebuilt the machine and reinstalled SQL so there souldn't be anything strange with the installation (all default).|||I wouldn't use Enterprise Manager for this. As I posted earlier, query the
server directly. What do you get when you run SELECT @.@.VERSION?
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Chad" <anonymous@.discussions.microsoft.com> wrote in message
news:D18A75A7-4AC6-4917-9334-F056D3E0159F@.microsoft.com...
I have done that as well to get the build number but under properties of the
sql instance name is where I was getting the information from Enterprise
Manager (is that wrong?). And after applying SP3a and the 8-11-03 patch it
hasn't changed the build information. I have taken the defaults for
installation of the SP and patch. I Have completely rebuilt the machine and
reinstalled SQL so there souldn't be anything strange with the installation
(all default).|||I get the original build number of the system (8.00.194). The patches don't seem to be applying or at least don't seem to be affecting the number at all and so the restore of the Master Database failes.|||Can't be right :-) I did this on various servers and I see updated build
numbers. You either applied the service pack to the wrong server, or you
haven't applied the service pack at all.
When you run the service pack exe first it extracts itself into a folder.
Many people mistake that and think they've applied the service pack, just by
extracting the service pack. Hope that's not the case with you. If it is,
you have to run the setup from the extracted folder.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Chad" <anonymous@.discussions.microsoft.com> wrote in message
news:E97EEE10-091F-4DD8-99EB-B9513B38F1B5@.microsoft.com...
I get the original build number of the system (8.00.194). The patches don't
seem to be applying or at least don't seem to be affecting the number at all
and so the restore of the Master Database failes.|||Narayana Vyas Kondreddi wrote:
>Can't be right :-) I did this on various servers and I see updated build
>numbers. You either applied the service pack to the wrong server, or you
>haven't applied the service pack at all.
>When you run the service pack exe first it extracts itself into a folder.
>Many people mistake that and think they've applied the service pack, just by
>extracting the service pack. Hope that's not the case with you. If it is,
>you have to run the setup from the extracted folder.
>
Vyas,
Whether or not this is what happened, it never hurts to remind people
how easy it is not to install the update:
How *not* to install sp3a for Microsoft SQL Server 2000
1. Download the service pack file, SQL2KSP3.exe, from Microsoft
2. Run the service pack file SQL2KSP3.exe
3. Click OK when you see the message "the package has been successfully
delivered"
Guess what? The service pack has not been installed! The download page
says you just need to "Install Database Components SP3a (SQL2KSP3.exe),"
so what's going on?
Youi wouldn't know it from the download page, but you now have to go to
the location where you extracted the files and run setup (and if I
recall, there are many files containing the word setup).
SK
>--
>HTH,
>Vyas, MVP (SQL Server)
>http://vyaskn.tripod.com/
>Is .NET important for a database professional?
>http://vyaskn.tripod.com/poll.htm
>
>
>"Chad" <anonymous@.discussions.microsoft.com> wrote in message
>news:E97EEE10-091F-4DD8-99EB-B9513B38F1B5@.microsoft.com...
>I get the original build number of the system (8.00.194). The patches don't
>seem to be applying or at least don't seem to be affecting the number at all
>and so the restore of the Master Database failes.
>
>