Hi, I have a real problem on my hand and I'm looking for some help. The persosn who used to be admin for our MOSS 2007 farm is gone. While he was with the company he did not take regular backups. Several of our databases have become corrupt. The database that houses our MySites is so corrupt that I can't even run dbcc checkdb on it. I have the same problem with our SharedServices_Search_DB. There are other site collection databases that I can run dbcc checkdb on, but they are cocming back with errors. I tried following this example in our dev environment http://trycatch.be/blogs/tom/archive/2008/05/12/fix-corrupted-database-through-stsadm.aspx but it didn't seem to work in our dev environment anyways. It shows how you can backup a site collection database and then restore it to fix corruption. I'm getting a ton of errors in both the SharePoint logs and on our SQL Server. Here's an example:SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:80; actual 0:0). It occurred during a read of page (1:80) in database ID 11 at offset 0x000000000a0000 in file 'G:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\SharedServices_Search_DB.mdf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online. I talked to a rep at Microsoft about this, and we came to the conclusion that this is not due to hardware issue, but was due to a bad migration into a virtual environment.Does anyone have any information or advice for me? I am not a SharePoint Admin, I'm a .net developer, but unfortunately the only person in my organization that can fix the problem.We are running MOSS 2007 with SQL Server 2005 backend. Let me know if any further info is needed. Thanks.

Hi,If I were in your place, I would go for the following try:to move a copy of SharePoint Content Database to a new SharePoint farm with a new SQL server DB (same versions OS and MOSS)Leave your old site and contentDB intact until you get the backup running on the new server, this way your ok if there is a problem to do so, follow the following steps:1) Find the content Database, These are listed under Central Admin->Application Management->Site Collection List2) Backup the content database,You could alternatively detach it, and copy it. Just doing a backup in SQL Server 2005 Management studio is easier.3) Restore content database to new server, Copy the BAK file to new server. Create an empty DB in Management Studio, restore from backup, you may need to change an option in the "options" tab of the restore dialog to get it to work. (Overwrite db). 4) Create Web App on new Server, Central Admin->Application Management->Create or extend Web App->Create New Web App. 5) Associate restored DB with new Web App, Central Admin->Application Management->SharePoint Web Application Management->Content Databases->Remove Content Database from your new web app.Now use STSADM to add restored DB to this web appc:\program files\common files\microsoft shared\web server extentions\12\bin on new server is where you can find the STSADM.run this command from there.stsadm -o addcontentdb -url http://yourwebapp:port -databasename yourcontentdb -databaseserver yoursqlserver6) Run ISSRESET from command prompt Best Regards, Ammar MCT

I had a bad feeling that that was what I would get back. Thanks for your help.

Look if you sharepoint database is get corrupted then you can do 2 things 1) use backup database and restore it (If you have latest backup), 2) Otherwise user sharepoint recovery software to repair your database.Sharepoint Recovery