On this page
Stops replicating a database, and promotes the secondary database to the primary database.
STOP REPLICATING db_name
This is used in inter cluster replication, when the primary database is down for some reason, and you do not want the secondary database to continue replicating from the primary, you run STOP REPLICATING on the secondary.
When replication stops, the secondary database is promoted to a primary database and it is fully available for both reads and writes.
If the previous primary database had running pipelines, these pipelines will continue to run in the promoted database.
This command causes implicit commits.
See COMMIT for more information.
This command cannot be reversed.
The remarks in the REPLICATE DATABASE topic discuss the replication and durability modes that a database uses after it has stopped replicating.
Refer to the Permission Matrix for the required permission.
STOP REPLICATING ExampleDatabase;Query OK, 1 row affected (0.04 sec)
Last modified: January 9, 2023