SAP LT Replication Server · SLT Fundamentals & Architecture

In SLT sizing, how do the number of data-transfer jobs scale across the Small, Medium, and Large T-shirt bands?

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 SLT Fundamentals & Architecture

SLT can filter data during replication — what three granularities of exclusion does it support, and why does that change a design decision?
In the SLT T-shirt sizing template, roughly what expected throughput separates a Small landscape from a Large one?
What underlying data-capture mechanism does SLT use to detect changes in a source table, and why does that choice matter operationally?
During the SLT initial load, does the source system have to be taken offline or locked for the tables being loaded?
If the target SAP HANA system goes down temporarily during replication, what happens to the ongoing data changes in the source, and what is the risk?
In the SLT data-transfer flow, what triggers deletion of a delta record from the source logging table?