SAP LT Replication Server · Replication Scenarios, Sizing & Deployment

You want source-system archiving to STOP deleting the matching rows in the SLT target. What must you configure, and what is the trap in that setup?

Sign in to see the full answer — free to start on the web.

This is one card from the KnowCard library. The full way to learn it — spaced-repetition review, progress tracking, and AI explanations — lives in the KnowCard app, free to start on the web. iOS & Android are coming soon.

Get started — it’s free

Already have an account? Sign in →

More in Replication Scenarios, Sizing & Deployment

For an exhaustive list of which non-SAP source systems SLT supports for data migration, where is the authoritative reference?
In SLT email notifications you can route alerts to different people. What is the routing dimension, and why use it?
Your landscape has 70+ SAP source systems that all need to feed one SAP HANA target. How many SAP LT Replication Server systems does this force you to deploy?
Two source systems must land in the SAME schema on the SAME SAP HANA target via SLT. Is that a supported multisupport configuration?
When choosing among the four SLT-to-SAP-HANA replication options (schema/system combinations), what primarily decides which one you pick?
In SLT, what does activating replication logging actually let you recover, and what is the recovery it does NOT provide?