[mgrollman]

I have an mdf file that was pulled from a cashed server (2005). Your demo was able to read all through the file, but of course I cannot test the save.

When I do save it, the output will be an mdf file. Can I take this file to a different SQL Server 2005 (since the old one is crashed) and somehow just attach it?

I seem to remember that SQL Server 2005 has a funny kind of closed-loop problem with migrating mdf files (as oppossed to bak files). The database must exist in order to try and connect to it, but if you make one up, then it will not let you attach the old one, becuase the GUID's don'make, or paths changed, or something.

Can you please describe what I can do with your product if I buy it, once the save has been done, given the above?

Cheers,

- Michael

[vrklsd]

Hi,
After repairing the corrupted database our software will save the data as a script.
Repaired folder will contain BCP files along with Commit.bat.
You have to take following steps for restoring all the data into MDF database:
1. Go to SQL Server Management Studio
2. Create a New Database
3. Go to Command Prompt (Start menu->Run->cmd )
Change the path to recovered folder ( cd PathName )
4. Run the Commit.bat file by typing commit.bat servername newcreateddatabase sqlserverusername sqlserverpassword > press Enter key and all tables will be copied to the new created database.