Acronym | Meaning | Remark |
sr | System Replication | This is the relevant replication in the Active/Active (read enabled) configuration |
atr | Asynchronous Table Replication | Another option to replicate data to another HANA database. You can find more information on ATR in the Asynchronous Table Replication section of the SAP HANA Administration Guide. |
resultcache | Result Cache | SAP HANA allows to cache the results of selects against views data for a given retention time. You can find more information on result caches in the SAP HANA Troubleshooting and Performance Analysis Guide. |
Client | http header Cache-Control | <Seconds> | Resulting HANA database hint | Effect |
SAP Fiori app via http/ODATA | Max-age = <seconds> | 1-59 | RESULT_LAG ('hana_short') | Data read from a secondary HANA database |
SAP Fiori app via http/ODATA | Max-age = <seconds> | >59 | RESULT_LAG ('hana_long', <value in seconds>) | Data read from a secondary HANA database if last synchronization with primary HANA database is not older than <seconds>. If there is in addition a result cache, this will be used if its last refresh is not older than <seconds> |
SAP Fiori app via http/ODATA | Max-age = <seconds> | 0 | RESULT_LAG ('hana_long', <value in seconds>) | Only fresh data read. If there is in addition a result cache, this will get refreshed |
Analytical client using e.g. INA protocol | n/a | n/a | RESULT_LAG ('hana_long') | Data read from a secondary DB. If there is in addition a result cache, this will be used. |
Continue to Part 5: Where was my data read from?
All parts of this blog series
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
13 | |
11 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 | |
4 |