Windows 7 Unpleasant problem with sql database

[melodycarey]

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.

 

[Neemobeer]

Were the databases moved properly? This sounds like the database(s) are corrupt. You may need to restore from a backup that you hopefully have. You could also try moving them back to the original system and run a DBCC CHECKDB command.

Side note, why are you running "important databases" on a Windows 7 box?

 

[AustGold]

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.

There are three different ways to restore mdf tool by steps below or the same query in Google or via SQL Server Solution
1) Recover the database manually with following command.
RESTORE DATABASE database_name WITH RECOVERY
2) Recover the database with the last log file.
RESTORE LOG database_name FROM backup_device WITH RECOVERY
3) Recover the database when bak is restored
RESTORE DATABASE database_name FROM backup_device WITH RECOVERY