mdf file in SQL 2012

Discussion in 'Web development / Programming' started by tobybyrne, Jan 26, 2016.

  1. tobybyrne

    tobybyrne New Member

    Messages:
    1
    Likes Received:
    0
    Hello everybody!

    I’m working with sql database for couple months. Today I have opened it and see pop-up window: “The header for file 'xxxx.mdf' is not a valid database file header. The FILE SIZE property is incorrect.”


    I don’t know what to do next, some ideas?


    Thanks in advance!
  2. NGEmu.com Advertisement

  3. Hatorijr

    Hatorijr Emu Author

    Messages:
    613
    Likes Received:
    1
    i have some experience with sql server 2012 (i use it with work), what are you attempting to do, so that i have some context in which to give suggestions as to how to proceed.
  4. codyallen

    codyallen New Member

    Messages:
    1
    Likes Received:
    0
    Guide below will help you with usual corruption of sql server data, but if it can't assist, then you may look at following resources for getting more methods


    https://www.repairtoolbox.com/sqlserverrepair.html SQL Server Repair Toolbox

    http://support.oreilly.com/oreilly/topics/it_seems_our_sql_database_is_corrupted?rfm=1

    http://www.sqlservercentral.com/Forums/Topic1602448-266-1.aspx


    Sometimes when you connect to your database server, you may find it in suspect mode. Your database server won’t allow you to perform any operation on that database until the database is repaired.

    A database can go in suspect mode for many reasons like improper shutdown of the database server, corruption of the database files etc.

    To get the exact reason of a database going into suspect mode can be found using the following query,

    DBCC CHECKDB (‘YourDBname’) WITH NO_INFOMSGS, ALL_ERRORMSGS

    Output of the above query will give the errors in the database.

    To repair the database, run the following queries in Query Analyzer,

    EXEC sp_resetstatus ‘yourDBname’;

    ALTER DATABASE yourDBname SET EMERGENCY

    DBCC checkdb(‘yourDBname’)

    ALTER DATABASE yourDBname SET SINGLE_USER WITH ROLLBACK IMMEDIATE

    DBCC CheckDB (‘yourDBname’, REPAIR_ALLOW_DATA_LOSS)

    ALTER DATABASE yourDBname SET MULTI_USER

    And you are done.

Share This Page