Skip to Content
Former Member
Feb 27, 2017 at 08:41 PM

Time Travelling in SAP HANA

133 Views Last edit Sep 18, 2017 at 09:08 PM 5 rev

We came across a few white papers on Time Travelling in SAP HANA but I was hoping to understand a few things:

1. Are there any differences in behaviour on HANA when using TIme Travelling on a runtime version of HANA vs Enterprise (eg Runtime - HANA as db under Banking Services or CRM etc) or are there alternative TT tech avail in such cases or on it's way?

2. In relation to TT, Should Auto Commit ever be switched off (requirement for TT to work) on a HANA DB when it runs as a dedicated DB for an SAP Solution?

Or is AUTOMCOMMIT OFF only applicable when developing your own apps? (Eg Enterprise HANA)

I don' feel comfortable with the fact that I now have to hammer M_TRANSACTIONS for the last_committed_Id or that I have to issue explicit COMMIT commands,

...Let alone consider the additional amount of space we may require for collecting history data over time for time travel.

We're trying to use the history capability for recoverability to a point in time if ever data gets hacked/broken and we don't have the luxury of restoring a full db (eg have to restore the entire landscape to the same pit, due to dependencies)

3.Any ideas where to find TT info per SAP Solution?