Replication to SAP HANA

When creating an SLT configuration to SAP HANA, what is the practical consequence of leaving the target DB connection 'managed by SLT' versus choosing 'Not Managed by SLT'?

After a source outage, which tables resume replication automatically and which must be restarted from scratch?

While the SLT server itself is down, the source stays up. What quietly grows, and what resource does it threaten?

The target SAP HANA system is down. What specific error does SLT raise, and when does the source logging table finally get cleaned up?

Across all three SLT outage scenarios (source down, SLT down, target HANA down), what is the common bottom-line about data integrity?

In the 'managed by SLT' approach, what determines the name of the schema created in the target SAP HANA database?

In the SLT configuration wizard for a HANA target, which field lets you point at an already-existing HANA schema instead of having SLT build one?

For an ABAP source replicating to HANA, what must exist BEFORE you create the SLT configuration, or the 'Specify Source System' step cannot complete?

When specifying the source RFC in an SLT config, what does enabling 'Allow Multiple Usage' actually buy you?

During SLT config, what does choosing 'Read from Single Client' change about which data is replicated from an SAP source?

On the Specify Target System step for a HANA target, which connection type do you select and what four HANA details must you supply?

Why does SLT's 'replication logging' feature let you recover a HANA target after data loss WITHOUT going back to the source system?

For the initial load into HANA, what is the difference between choosing 'Performance Optimized' load mode and choosing the 'Real Time' replication option — are they the same setting?

What governs how many data transfer, initial load, and calculation jobs an SLT-to-HANA configuration needs, and can it be changed after creation?

After creating an SLT configuration, what unique identifier is generated that you must select in LTRC to work with that configuration's tables?

In LTRC, which tab and button do you use to actually start replicating a specific table like SFLIGHT to HANA?

In LTRC's Data Transfer Monitor, a table's sequence number shifts from 30 to 40. What does that transition tell you?

You have one huge table and several small ones in an SLT-to-HANA config. What sequence number should you assign the large table, and why?

How many database triggers does SLT create in the source system for a replicated table, and what do they cover?

Which source-system transaction lists the SLT triggers created for a table (with their creation timestamps)?

During replication, which LTRC Expert Functions report shows you the changes still pending (not yet written to HANA)?

Where does the SLT calculation job actually run — on the SLT server or the source system — and how do you monitor it?

On the SAP HANA target side, what additional replication logic must you implement for inbound SLT replication?

On the SLT server itself, what component sits between the read modules and the write modules, and what guarantee does it provide?

The source system for an SLT-to-HANA config goes down mid-replication. What happens to the DATA, and what should you do about the log noise?