Post reply

Any feature/way to re-do my update/delete/insert without using transaction

  • January 30, 2007 at 7:13 pm

    #90944

    Hi,

    It is know that using transaction, we can un-do any update/delete/insert.

    However, we want to be able to un-do any user update/delete/insert statement

    even after it is done a few days ago.

    I come across some third-party tool that can generate un-do statement

    for the last action(update/delete/insert) done, is there any way to do similar stuff

    in sql server 2000 or 2005 ?

  • January 30, 2007 at 8:57 pm

    #686698

    Not after a couple of days... unless you have a really good audit log.

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • January 31, 2007 at 7:42 am

    #686846

    A third party tool will allow you to generate the reversing entry if you still have the logs from a few days ago.

    The problem is that other things outside the transaction could change because of the transaction. Perhaps this is a deposit that you want to reverse in a bank situation. However since the deposit, other withdrawals have occurred, which would result in a negative balance if you reverse the deposit.

    This happens in the real world and when it does you get hit with a note that you owe the bank the money + service charges. In supply chain, inventory, etc. situations, this can cause problems if you try to undo somethign without knowing the impact.

  • January 31, 2007 at 8:28 am

    #686871

    Yep... some serious truth in that... the best accounting procedure is, of course, don't make mistakes.  The second best is don't try to roll back anything... issue a credit!

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

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

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