GilaMonster (9/13/2011)

---

halifaxdal (9/13/2011)

---

GilaMonster (9/13/2011)

---

Run SP_configure and set allow updates to 1. Update sysdatabases for that database and set the status to 32767.

Then see if you can access the DB and run checkdb. Not repair, just with the no_infomsgs and all_errormsgs options.

There's far more wrong here than just a suspect DB. You've got access violations all over the error log. This is one sick server. I'd suggest calling CSS, but SQL 2000 is out of support so they won't help you.

Your also running on a very low service pack of SQL 2000. SQL 8.0.818. Offhand I don't know what service pack that is, but it's not the last one available. I strongly suggest you patch that server to the latest service pack and consider an upgrade to 2008.

I certainly will try your advise and for sure I will upgrade it to 08/05 if I will be designated to take over this server/db, for now, I just want to try my best effort to see how much I can get the data back.

818 is SP2, can't believe it, eh? Me too.

p.s. That should not be done on the production server...