Перенос доработок на Prod

[ax_mct]

Цитата:

Сообщение от Logger

Интересно, а как в других ерп эта проблема решается?
Если тот же сап крутится на sql, то синхронизация займет схожее время. Или нет?

https://blogs.sap.com/2015/03/11/min...-of-an-update/

In principle two approaches are used:

• Clone
• In place

...
The clone approach needs a full copy of the productive system but it is very flexible regarding maintenance activities.
...
nZDT (near Zero Downtime Service)
The nZDT is a service offered by SAP. It is a customer specific procedure that is technically a clone approach.
When using the nZDT service, the maintenance is performed on the clone of the production system. All changes are recorded and transferred to the clone after the maintenance tasks are completed. During the final downtime, only a few activities are executed, including a switch of the production to the new system (clone).
....
ABAP applications, especially the ERP system with DB sizes in range of several terabytes. Therefore the SAP standard tools use the in place approach for ABAP systems in general to minimize the planned downtime. The in place approach uses the DB and needs a minimum of additional Hardware. The downtime minimization capabilities of SUM, e.g. nZDM, use a separate DB schema (shadow).