SAP LT Replication Server · Scheduled Downtime & Recovery Procedures

Contrast the on-prem-to-cloud transition with the source database-migration scenario: why does one require dropping/recreating logging tables while the other does not?

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 Scheduled Downtime & Recovery Procedures

In the DB-migration scenario, when you finally click Activate on the SLT config, what does that single action create in the source — and why is that broader than in the upgrade scenario?
When recreating SLT triggers after a source upgrade, what must the configuration's state be, and which report do you run?
After a DMIS upgrade completes, there is a final step you must NOT skip before releasing the system — one that has no equivalent in a plain NetWeaver upgrade. What is it?
Why is locking users the mandatory FIRST action before deactivating an SLT configuration for planned source downtime, rather than just deactivating directly?
After locking users but before deactivating an SLT config for downtime, why do you wait a few minutes and re-check the logging table instead of deactivating immediately?
When running View Unprocessed Logging Table Records to confirm the logging table is drained, why sort the output descending rather than accepting the default order?