SAP HANA 2.0 Administration · Database & Tenant Administration

After copying a tenant by SAP HANA database replication, the encrypted target won't start / loses customer config. What did replication NOT bring across that you must restore manually?

Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.

This is one card from the KnowCard library — thousands more across SAP, Linux, Python and more. In the app you get the answer, AI explanations, and cards that come back right before you would forget them. Free to start on iOS, Android or the web.

More in Database & Tenant Administration

On SPS 01+, you drop a tenant database and assume its backups are gone with it. Why might that assumption now cost you disk space or a compliance miss?

You must move ONE tenant (not the whole system) between SAP HANA systems with near-zero downtime. Which copy/move method fits, and why not the others?

You try to set up SAP HANA database replication and it refuses to start. Which two tenant-side preconditions are most often the cause?

You need to revert a tenant to its fallback snapshot. What is the step practitioners forget that makes the single START statement fail?

You're restoring an encrypted SAP HANA database to a DIFFERENT system. Why does ordering matter, and what fails if you get it wrong?

A client needs to reach a HANA tenant but the tenant's individual SQL port may change if it's moved or recreated. Which connection style survives that, and what's the trade-off?

Start learning today

Free to start — download the app or use it in your browser.