March 14, 2018 at 7:56 am
I like to use MS SQL Server databases. In our company, we have some huge very valuable database. Some hours ago, we've started to transfer it from one machine to another. Now we've almost done. But one of the databases on new machine has started to show up a message The header for the file WorkingD.mdf' is not a valid database file header. It has happened at opening. What it might be? How to solve it in couple of days? We are on SQL Server 2008 under Win 7 x32.
March 14, 2018 at 9:03 am
laurelrom - Wednesday, March 14, 2018 7:56 AMI like to use MS SQL Server databases. In our company, we have some huge very valuable database. Some hours ago, we've started to transfer it from one machine to another. Now we've almost done. But one of the databases on new machine has started to show up a message The header for the file WorkingD.mdf' is not a valid database file header. It has happened at opening. What it might be? How to solve it in couple of days? We are on SQL Server 2008 under Win 7 x32.
I'm afraid this looks like a corrupt file. The best way to recover is restoring from a up-to-date backup.
How did you transfer the database?
If you are copying the MDF and LDF files, did you on forehand shutdown the SQL Server service on the originating server or at least performed a DETACH of the database?
The safest and probably the most used way to transfer a database is by creating a backup on the originating server and restoring this backup on the destination server.
March 18, 2018 at 11:34 am
This was removed by the editor as SPAM
April 30, 2018 at 11:27 am
This was removed by the editor as SPAM
April 30, 2018 at 11:28 am
This was removed by the editor as SPAM
June 21, 2018 at 9:33 am
This was removed by the editor as SPAM
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply