November 13, 2010 at 10:17 am
Hello, I recently had one MS Share-point content database corruption of my SQL 2005 after a power failure when an update was going on. I
managed to get it from suspect to Emergency Mode, in this mode I could access the tables and all the store procedures.
I tried to create a replica database of the corrupted one, using Script Database As --> Create To ---> New Query Editor Window, on the old
database. I now exported all the tables into the new database. After, I detached the older one, renamed the new one to the old one's name
both physically and logically, without any errors.
Now when I tried to let the launch back the web portal and it gave me errors as if the new database didn't match the older one.
What did I not do right? and should I have used any special tool to recreate a whole new database from that Emergency mode Database?...
November 13, 2010 at 12:31 pm
Without seeing what exactly those errors are, no way to tell.
Did you recreate all the procedures, functions, views etc that may have been there?
Was recreating the DB necessary? No good backup around to restore? Was the cause of the suspect status irreparable?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply