Post reply

Repair a database (my worst case ever!!!)

  • January 26, 2004 at 9:39 am

    #160727

    I had a problem with my HDD, so I had to send it to a company that recovers data from damaged disks. In result they sent me a DVD with the content os my hard disk, in witch I had around 15 databases.

    Of all my databases only 3 did not attach smothely to the new SQL server.

    In 2 cases I had to create a empty database, and after stoping the SQL Server service, renaming the recovered files and copying them to the location of the newly created databases, I had the databse in the server (suspect, ... but they where there)

    In these cases I just had to alter the STATUS in MASTER..SYSDATABASES to put the database in recovery mode like this

     

    USE MASTER

    SP_CONFIGURE "ALLOW UPDATES", 1

    RECONFIGURE WITH OVERRIDE

    UPDATE MASER SET STATUS=-32768 WHERE NAME='xxx'

     

    Afterwards I made a

    DBCC CHECKTABLE (table; REPAIR_ALLOW_DATA_LOSS)

     

    and I recoverd the data from the tables

     

    Now I am trying to recover this last database, But I am havig really bad luck.

    After attaching the database using this method the databae dis not apeared in Enterprise Manager as SUSPECT (strange at least). I tryed to view the contents of my tables in Enterprise Manager I got the following error:

     

    Error 3624

    Location: p:\sql\ntdbms\storeng\include\record.inl : 1447

    Expression m_SizeRec>0 && m_SizeRec<=MAXDATAROW

     

    I tryed puting the STATUS to  -28672, and in Enterprise Manager I have the visualization os the database in single user mode, but still when I try to do a BDCC CHECKTABLE(table, REPAIR_ALLOW_DATA_LOSS) I get the information that I have to put the database in single user mode (?????)

     

     

    I need some help guys, ....

    Thanks

  • January 26, 2004 at 11:43 am

    #491660

    hello jose

    i was have a similar problem

    i follow the next step for solve this problem

    1. put my db in single user

    2. first run DBCC CHECKDB (databasename, repair_allow_data_loss)

    3. after run DBCC CHECKDB (databasename, repair_fast)

    this was everything

    this other commando who to probably can serve you

    DBCC CHECKDB (databasename, REPAIR_REBUILD)

    Good look

     

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply