Data consistency after rollback

Not applicable

Data consistency after rollback


currently we are solving problems with data consistency after rollback.

During a solution deployment we proceed in these steps:

  1. prepare a new version of a table for a new solution (X-table)
  2. rename original table to Y-table and rename X-table to table
  3. then, with a certain lag, we might find an error in new SQL scripts of the new solution and go for a rollback:
    1. rename table to X-table
    2. rename Y-table to table

But in-between 2) and 3) several data operations take place and are lost !!

Is there any tool or workaround preventing rollback from damaging data consistency ?

Thank you very much for your tips.