Skip to Content

How to preserve / recreate Hana change list after database restore

We need to restore our DEV Hana database to an earlier date (previous week), but how do we best handle incomplete change lists, or change lists that have been sent to QA for testing, but is not in production yet?

We have already exported the delivery units to backup all development work that has been done until now, and we plan to import those back into the DEV system once the database restore is complete. That way all development work on views over the past week will be restored. Some of these views were attached to change lists that were not completed and released yet. Will this pose a problem going forward when we continue development and attach the view to a new change list? I assume the change list numbers will not be the same as before.

Will the new change list contain all the changes needed to update QA and PROD? The versions of the HANA views will be different between DEV and QA / PROD.

What about views that was released to QA for testing, but have not been imported into PROD yet? Should we complete these transports to PROD before we do the restore? The change list numbers will not be the same after the restore is done.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

0 Answers