A customer has provided me with a back up file which he says is from SQL Server 2005 Compact Edition. I'm unable to restore it in either of the following instances I have on my machine
1. SQL Server 2014 (via Management Studio 2014)
2. SQL Server 2005 (via Management Studio 2005)
In both cases, if I try to use the GUI to restore, it just doesn't show any backups in the file.
When I restore with the following backup command...
RESTORE DATABASE Framework FROM DISK = 'C:\SQLBU\Framework.bak'
I get the following error in 2005 and 2014...
Msg 3241, Level 16, State 0, Line 3
The media family on device 'C:\SQLBU\Framework.bak' is incorrectly formed. SQL Server cannot process this media family.
Msg 3013, Level 16, State 1, Line 3
RESTORE DATABASE is terminating abnormally.
I download SQL Server 2005 compact edition, but the install didn't allow me to create a named instance? (Not sure if something went wrong, I tried to google to see how the compact edition works, but it is so old I'm not getting any useful results) Can anyone tell me 'how do I create a 'compact edition' instance' (so I can try to restore to that) ? Or any other solution that will enable me to restore the .bak (so I can port it to a newer version of SQL Server)
Thanks to anyone who can help! 🙂
Do you know how the backup was taken, was it with any third party products?
You may also want to try executing:
FROM DISK = 'C:\SQLBU\Framework.bak'
If that doesn't work it could just be a corrupt backup.
The backup is auto generated, so I only know it is 'SQL Server 2005 Compact Edition'
Thanks for the suggestion, but the 'HEADERONLY' command generates the exact same error.
dave 12950 - Wednesday, April 26, 2017 4:15 PM
Duh...now that I thought about it, CE backups aren't in the same format anyway. I thought they had a different extension by default as well. You used to use some export tool that comes with CE and it exports the database to a .sql file. Maybe the customer renamed it and it is a .sql file? Who knows - it might be worth making a copy, renaming the extension to .sql and see if you can open it in notepad.
You probably need to ask the customer what steps they took to make the backup.
Thanks for the reply.
The backup is auto generated by his legacy software, and named with a .bak extension. Opening it in notepad shows a mixture of binary symbols and some readable sql text....(screen capture attached)
Thanks a million for pointing me in a good starting direction. Really appreciate your time!!
This was removed by the editor as SPAM
Viewing 8 posts - 1 through 7 (of 7 total)