Restore master db version problem

[pcawdron]

We've had two SCSI HDD fail on our SQL Server 2000 absolutely bring it to its knees. No data could be recovered, it's allllllllll gone.

I've set up a new server, win 2000. Installed SQL Server 2000, with SQL Slammer patches applied (exactly the same patches were aplied to the old server). I've restore all the various db's from tape, switched to single user mode from a dos prompt (sqlservr.exe -m -c)

But... when I try to restore the master SQL Server tells me that I cannot restore the master db from a different version. It then gives me some long winded number like 21342567 and tells me that the old version is something like 2134632 (I'm at home now and don't have the exact numbers in front of me)

What's up? They were both SQL Server 2000, same patches... Although they may have been installed from different CDROM's.

Anyway around this or is it all gooooonnnneee?

I'm specifically after all the DTS packages in the master db, nothing else.

Any thoughts

As always, I'm incredibly grateful to the tek-tips community for their remarkable support and encouragement in solving problems like this. You guys are great...

Cheers,
Peter

 

[SQLBill]

When your original SQL Server was first installed, what version SP did you have on it? Try installing it with that version, then upgrading it.

-SQLBill

 

[Corran007]

also all the dts packages are in the msdb database, not master. if thats all you care about, just restore that.

Though the version differcne is odd.

 

[pcawdron]

Thanks for the tip about msdb, unfortunately it produces the same error, it is....

SQL-DMO - The backup of the system database on device... cannot be restored because it was created by a different version of the server (134218262) than this server (134217822). RESTORE DATABASE is terminating abnormally.

Also, I'm not sure what version SP was originally on it, it's been around for years and undergone several upgrades and service packs. It was SQL Server 2000, though, so it should be compatible,

Looks like I'm off the the Microsoft site for a bit of searching....

 

[pcawdron]

I found this on the Microsoft site, and it allowed me to clearly identify which versions we have been using

http://support.microsoft.com/default.aspx?scid=kb;en-us;264474

Old, crashed SQL Server = 8.00.534
New, SQL Server = 8.00.194

Remarkably, then, it's simply that I hadn't applied SP3 to the new server. In otherwords, it's not that the old version was old, it was too new!!!

So I still had the software from the last SP applied to the old server, SP3. I ran that but.... it's leap frogged and has gone from 8.00.194 to 8.00.760 so I still get the same error.

Arghhhhhhhhhhh!!!!!!!!!!! Microsoft, why do you do this to us? WHY????

I've searched high and low on the Microsoft site and can find NOTHING that stipulates what version each SP represents. My only option now is download SP1 and SP2, uninstall SP3 and see if one of these matches 8.00.534

This is extremely poor on Microsoft's part, I'd get fired if I developed something this shoddy

Any more thoughts?

Cheers

 

[SQLBill]

Where did you get this idea:
Remarkably, then, it's simply that I hadn't applied SP3 to the new server. In otherwords, it's not that the old version was old, it was too new!!!

Here's how the versions REALLY convert:

Old, crashed SQL Server = 8.00.534
***SQL Server 2000 with SP2.01

New, SQL Server = 8.00.194
***SQL Server 2000 NO SERVICE PACK

Solution, your new SQL Server needs upgraded to SP2.01
Then once everything is recovered, upgrade to SP3.

-SQLBill

 

[pcawdron]

OK... thanks... I was stabbing in the dark on versions because I couldn't find any documentation on what number matched up with which SP

Cheers,
Peter

 

[SQLBill]

Check out

http://www.sqlsecurity.com

and Select the link for SQLSecurity Checklist.


-SQLBill

 

[SQLBill]

Also check out FAQ183-3159.

-SQLBill