Asynchronous-commit mode
An availability replica that uses this availability mode is known as an asynchronous-commit replica. Under asynchronous-commit mode, the primary replica commits transactions without waiting for acknowledgement that an asynchronous-commit secondary replica has hardened the log. Asynchronous-commit mode minimizes transaction latency on the secondary databases but allows them to lag behind the primary databases, making some data loss possible
Synchronous-commit mode.
An availability replica that uses this availability mode is known as a synchronous-commit replica. Under synchronous-commit
mode, before committing transactions, a synchronous-commit primary replica waits for a synchronous-commit secondary
replica to acknowledge that it has finished hardening the log. Synchronous-commit mode ensures that once a given secondary
database is synchronized with the primary database, committed transactions are fully protected. This protection comes at the
cost of increased transaction latency.
Submitted questions and answers are subject to review and editing, and may or may not be selected for posting, at the sole discretion of w3Sniff.
Get Started
Comments
Leave a Comment