7.0 disaster HELP!!!!!!!!!!!!!!!!!!!!

[timscronin]

We lost power in the midwest and I have been informed I have a sql 7.0 disaster. (Of course if was a database and server I never heard of, runs as a msde for Crystal reporting server, and low an behold, never been backed up)
Now that I am past griping, when I try to start sql server on the box I get
18052 :
Error: 3624, Severity: 20, State: 1..
17052 :
Cannot recover the master database. Exiting.

Any ideas other than screaming. I did find a product at this site

http://software.techrepublic.com.com/download.aspx?docid=227574

Any other ideas?

 

[Catadmin]

You need to find the documentation (check the FAQ site here) for recovering the Master DB. Also, I believe you're going to need the install CD/Disk (Hope you have it lying somewhere around).

Once you restore the master DB, you should be able to recover the server, but you may not be able to recover the database if it's never been backed up.



Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"

 

[timscronin]

that's what I am afraid of, I have seen 2 references to this recovery tool in searches

 

[mrdenny]

Try grabbing the mdf and ldf for master from another SQL 7 server. Try dropping them into place where the corrupt ones are (backup the corrupt ones first) then start the server. You'll get a bunch of errors when it starts, but it should start. If it doesn't try starting the server in single user mode. Then you should be able to hack the sysdatabases table to get it to see only the system databases (and have it see them in the correct place). Then you can try to reattach the user databases that are needed using the sp_attach_db procedure.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com