NZDT
An upgrade technology option officially provided by SAP that captures business changes during an upgrade through database triggers and replays them after the switchover, minimizing the interruption time for write operations.
Timeline (last 90 days)
SAP's NZDT (Near-Zero Downtime) is an official upgrade technology option that captures business changes during the upgrade via database triggers and replays these changes after the system switch, minimizing the interruption time of write operations.
The "zero downtime" in NZDT only refers to minimizing the write-lock window at the technical level; the system remains readable for most of the upgrade, but write operations are locked, so it is not completely imperceptible at the business level.
For medium-sized systems, a well-prepared NZDT upgrade write-lock window is typically 2 to 4 hours.
For large systems with large data volumes and extensive custom ABAP code, the write-lock window of an NZDT upgrade expands significantly.
Vendors' benchmark data comes from reference systems—optimal hardware, a clean codebase, controlled data volumes—which differ from the actual environment of production systems.
The NZDT switch in the case described in the article actually took 14 hours to release the write lock, during which 847 IDocs accumulated in the queue.
All Facts (6)
SAP's NZDT (Near-Zero Downtime) is an official upgrade technology option that captures business changes during the upgrade via database triggers and replays these changes after the system switch, minimizing the interruption time of write operations.
50%UnverifiedThe "zero downtime" in NZDT only refers to minimizing the write-lock window at the technical level; the system remains readable for most of the upgrade, but write operations are locked, so it is not completely imperceptible at the business level.
50%UnverifiedFor medium-sized systems, a well-prepared NZDT upgrade write-lock window is typically 2 to 4 hours.
50%UnverifiedFor large systems with large data volumes and extensive custom ABAP code, the write-lock window of an NZDT upgrade expands significantly.
50%UnverifiedVendors' benchmark data comes from reference systems—optimal hardware, a clean codebase, controlled data volumes—which differ from the actual environment of production systems.
50%UnverifiedThe NZDT switch in the case described in the article actually took 14 hours to release the write lock, during which 847 IDocs accumulated in the queue.
50%