Update more efficiently
Acceleration/table export: up to 4 times faster. The larger the table and the higher the effort for sorting, the greater the time gain during export.
As mentioned above, an SAP system copy created for updates is a special use case of homogeneous system copy. Here, a production system represents the source and a non-production system with a specific long-term task in the SAP system landscape represents the target. The most common update scenario involves updating a QA system in the SAP transport system.
SAP system copy and the cloud
Table splitting reduces the risk of losing a lot of time during export in case of an error. When restarting, the complete table does not have to be exported again, but only a subset. Simultaneous processing of a table by several R3load processes can reduce the total runtime for this table.
For a long time, manual procedures dominated, supported by SAP (guidelines), in particular by predefined procedures and a large number of checklists. In many places, this was supplemented by scripts created in-house, which, however, only automated partial tasks/processes of an SAP system copy.
The tool "Shortcut for SAP Systems" is excellently suited to complete an SAP system copy easier and faster.
Different DDLORA* files can be assigned to the R3load packages.
In the past, the cost of a refresh, i.e., updating the environment with new data, often corresponded to the cost of the initial setup.