We have a client that uses Dynamics GP 10 and recently suffered some sort of power loss to their building that seems to have possibly caused some serious data corruption on their Dynamics / SQL data. I'm told that the server itself didn't ever lose power (due to being connected to a UPS), but everything else did including the network and potentially open connections from workstations to the server.
Unfortunately, this client has now been down for several days and I'm just coming into this situation today. They've been working with Microsoft SQL support, but I'm wondering now that I've spent the better part of the day working with MS SQL support as well if that was the right department to handle this or perhaps they should have been working with Microsoft Dynamics GP support?
I don't know what steps have been taken over the past several days, but am also worried that further problems might have been caused by inexperienced troubleshooting. I am only vaguely familiar with SQL Server 2008 and Dynamics GP 10, so any help that could be provided on here would be greatly appreciated. As far as I know, they can get into the Dynamics GP company file, but numerous actions they take in there are returning SQL and other errors now and so they can't get to most of the functionality they need.
I also believe that DBCC checkdb with repair_allow_data_loss was run against the database and returned several errors, including:
Msg 7985, Level 16, State 2, Line 1
System table pre-checks: Object ID 3. Could not read and latch page (1:73526) with latch type SH. Check statement terminated due to unrepairable error.
DBCC results for '<DATABASE_NAME>'.
Msg 5233, Level 16, State 98, Line 1
Table error: alloc unit ID 196608, page (1:73526). The test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. The values are 62916617 and -4.
CHECKDB found 0 allocation errors and 1 consistency errors not associated with any single object.
CHECKDB found 0 allocation errors and 1 consistency errors in database '<DATABASE_NAME>'.
They don't have any good normal backups, although they did have CrashPlan PROe installed and it has been set to backup the DATA directory (among other directories) located at D:\Data\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA
I'm told that the power outage occurred sometime in the afternoon on 12/15 and the corruption and errors and access issues started shortly thereafter, and yet it does appear there are MDF and LDF backups for the database in CrashPlan PROe from 12/15 3:30 AM (the next previous backup is early November I think).
The problem is that even after we recovered the MDF and LDF files, we can't seem to get anything working with them. We tried replacing the MDF and LDF files in the DATA directory with the recovered ones, and that doesn't seem to have helped (although after putting the database back into multi_user mode we could access it via GP and get to some data, but are still getting a lot of errors for most things), and also through a lot of work and trial-and-error with MS SQL Support we managed to extract most of the table data from the corrupted database and set-up a new company and then imported that data into the new company database, but that didn't seem to provide access to any of the data either. Obviously we're grasping at straws here, partly because I'm completely unfamiliar with these products and partly because (as mentioned above) I'm wondering if MS SQL support was the right team to assist with this.
If anyone has any help or advice (that they can provide in relatively idiot-proof steps) it would be GREATLY appreciated. Feel free to ask any questions and I'll answer as quickly as I can. Thanks!!
P.S. I'm also wondering if the 12/15 database restore might also be corrupted which is why nothing we've tried has worked either, in which case I'm wondering if we should just try (hopefully with some guidance and help from those of you experts on here) recovering from the early November MDF and LDF backed-up files (if that's possible). Thanks again for any help!
Marc
*This post is locked for comments