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?

What is the default data retention period for SLT replication logging, and why does the default matter operationally?

You need to turn on replication logging for a configuration that is already live. Where do you do it, and where do you NOT?

By default, does SLT replication logging apply to every table in a configuration or only to selected tables?

SLT stores logged replication data in two different tables depending on the source table type. Which table holds data read from SAP cluster tables?

A record in a replicated source table gets archived. What does SLT do to the corresponding row in the target by default, and why?

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?

During SLT replication a network interruption causes duplicate-key constraint violations in the target. What single setting resolves this, and why does it work?

Migrating master data vs. transaction data with SLT — which data provisioning option fits which, and why does the choice matter?

SAP Data Intelligence Cloud rejects null values arriving from SLT. How do you handle nulls without pre-cleaning the source?

For selective SLT data migration, what capability lets you move only a subset of records, and what kind of criteria does it key on?

SLT's automatic recovery keeps retrying connections after a comms failure. What second-order data problem can that same behavior create, and how do you pre-empt it?

You need to cut SLT migration runtime for a huge table load. What is the standard tactic and where is it configured?

The SLT health-check job flags a 'Logging Table Check' alert. What threshold-based condition triggers it, and what does it tell you?

The SLT Latency Check can raise an alert. What exactly does it measure end to end?

SLT email notifications rely on a background job. What is its resource footprint, and why is that a selling point over manual monitoring?

For a replicated source table, how many database triggers does SLT create, and what determines whether it's three or four?

In an SLT logging-table entry, which column tells you what kind of DML operation the record represents, and what value flags an archival?

Where does SLT physically create its replication triggers and logging table — source system or SLT system?

SLT is pitched for both data migration and data consolidation. What is the defining difference between these two use cases?

During SLT data migration you finish replication. What is the required next step before declaring the migration done, and why can't you skip it?