Problem while attached the database

Question

Post reply

Problem while attached the database

Satisha

Valued Member

Points: 63
More actions
August 4, 2006 at 1:24 am

#169226

Hi,

My Client is facing some data losss and also his machine was corrupted. so they copied the database file (mdf) directly from SQL server installation path (c:/program files/SQL Server/MSSQL/data/) from his machine and sent, i am trying to attach that database to my SQL server datbase for analysis i am getting one Error message box with the following message while trying to attach.

Error 3624
location: recovery.c:2412
Expression: seenCkptdEnd
SPID: 51
Process ID: 1820

Anybody has a solution for this

With regards
Satisha

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Salil Sunil Sule-353027 SSC Enthusiast Points: 153 More actions · Answer 1

HI,

Check out if this link is useful for u:-

http://support.microsoft.com/kb/825197/

Also use dbcc checkdb and dbcc checktable for checking the corruption.

bye

Salil

ntdoc Valued Member Points: 58 More actions · Answer 2

Well this was posted in the SQL 2005 forum so if that KB does apply then this post is in the wrong forum as that KB is for SQL 2000 and ultimately resolves the issue by installing a Service Pack for SQL.

I agree the checks are good though.

Neil Coombes Valued Member Points: 64 More actions · Answer 3

I have had this sort of scenario before and found that because I could not attach the database I could not run commands such as dbcc checkdb (if you have access to the original machine then you should try running it on that to get the data in a better state before taking a copy of the mdf (and ldf if possible).

Anyway assuming that you just have an mdf file which you can't attach to your db engine the only useful tool I have found is Recovery for SQL. Basically you point it at an mdf file and it extracts everything it can find to a load of sql scripts which you can then use to rebuild your data on a blank database. The only problem I have found with this tool is that at the rebuild stage it wants to run the schema file first which means that the data can't be added back in as it tends to fail the constraints because the tool has no chance of knowing what order it should being adding the data in to satisfy the constraints on the tables.

If you find you have this same problem then you may need to create a blank database run the schema script and then remove any constraints it creates. and then recreate the constraints once the data is in place.

Anyway if your interested the tool is availble from the website below for $499 and it has saved a couple of my clients data who were in the same scenario you described.

http://www.officerecovery.com/mssql/index.htm

If anyone knows of other tools like this that they have used successfully then I would like to know about them too (especially if they are free) as you can never have too many recovery tools.