Any way to restore transaction files out of sequence?

  • Hi,

    Due to lack of planning, I have come across a situation where I need to restore a transaction log, but I am missing a log file for a short period of time between the last full backup of the database and the point in time at which I need to restore. 

    I am really just trying to restore one table in our db that a developer inadvertently deleted.  I have restored the full backup of our production db to a test db.  Now I would like to restore the day's tx log file to the test db.  The problem is that I'm missing a log file for about 1 hour of transactions that occurred after the full backup.  I was hoping there would be some way to spoof SQL Server into allowing a tx log to be restored out of sequence.  The table in question would not have any transactions that would be in the missing tx log file.

    Any help or suggestions are greatly appreciated.

     

    Thanks,

    Derek

  • No way, Sorry.

  • You might be able to use a tool like Lumigent's Log Explorer.  You could restore the full backup to a new database.  Then you might be able to use Log Explorer to go through the logs, replaying any transactions against that table up to the point at which it was dropped.  Once that is done you could move the table and data into your original database. 

    This process is not without some risk (you might miss some transactions etc...) and it may be a lot of work, but without a complete series of log backups there is no other way I can think of.

    /*****************

    If most people are not willing to see the difficulty, this is mainly because, consciously or unconsciously, they assume that it will be they who will settle these questions for the others, and because they are convinced of their own capacity to do this. -Friedrich August von Hayek

    *****************/

  • DC,

    Thanks for the info.  I requested a price quote from Lumigent several hours ago, but I have yet to receive one.  Meanwhile the lost days work is almost regained (manually).  I'll still take a look at the product in case we ever need anything like this again.  I have created the process flaw that caused the break in tx log continuity (data loss is a strong motivator!). 

    Anyway, thanks for the help.

     

    -Derek

Viewing 4 posts - 1 through 3 (of 3 total)

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