tosmserversupport
asked on
SQL 6.5 DAT File Import to SQL 2000/2005
A SQL Server failed that hosted a SQL 6.5 database. We performed a backup of the database using the built in backup tools within SQL 6.5. File is a .DAT file. The orginial MASTER database was corrupted when the server failed and now I cant get the backed up .DAT file to restore to another SQL 6.5 or newer database. Used a demo software, Recovery for SQL Server 3.0, to look at .DAT files data and it was intact, but dont want to spend the $500.00 for the program. What is the best way to attach the .DAT file to a newer SQL instance and export the data?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
When I go through the Restore process on a clean SQL 6.5 instance and try to restore the database from the DAT file I have, which is patched to the same level as before, The button to perform the Restore is grayed out.
I have tried to attach the DAT file as a SUSPECT DB and resetting the status flags but that does not work either.
I have tried to attach the DAT file as a SUSPECT DB and resetting the status flags but that does not work either.
Hi,
Try using the command-line to restore as another database ... This will a) prove that you can restore the database, b)allow you to use DTS and wizards to upgrade the database to either SQL 2000 or SQL 2005 c) you don't have to overwrite the existing database ...
Cheers
David
Try using the command-line to restore as another database ... This will a) prove that you can restore the database, b)allow you to use DTS and wizards to upgrade the database to either SQL 2000 or SQL 2005 c) you don't have to overwrite the existing database ...
Cheers
David
ASKER
What would be the syntax for the restore to another database. I am having problems locating syntax on the web, I guess due to age of 6.5...
ASKER
for the interest of time, we just purchased the software and went on with business.
however, you will need to apply the same service pack that what you had before, with a "bare" sql 6.5 you might indeed get those problems.
what are the errors you get?