Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

SPS 2003 Content Database corrupt

  Asked By: Helen    Date: Feb 24    Category: Sharepoint    Views: 1408

I have a single SPS 2003 content database for our site that has become
corrupt (on the SQL level) from a SQL torn_page when one of the drives
went down. My questions are, can I just restore from the last good
database backup directly over-top the corrupt database and the site
won't know the difference? Or, could I just add a second content
database for the site, and then delete the original, corrupt content
database?

Share: 

 

1 Answer Found

 
Answer #1    Answered By: Joanne Greer     Answered On: Feb 24

If you add a new content  database, and remove the old one, well you'll loose all
your data that way.
Also, if it's the Default content database  for the portal, Portal prevents you
from removing/adding that database from the Manage Databases page in WSS Central
Admin.

If you restore from a known good backup, you'll still need to detach/reattach
that database in WSS Central Admin, so that the "Site discovery" detection will
run and update the Configuration Database appropriately (in case new sites were
added since that backup, those would still be listed in the Configuration
Database)

What I would suggest, is you restore the known good backup, then run the orphan
detection operation of STSADM, but you'll need the hotfix as described here:
blogs.msdn.com/.../652453.aspx

 
Didn't find what you were looking for? Find more on SPS 2003 Content Database corrupt Or get search suggestion and latest updates.




Tagged: