v.25.10Improvement
Change for SYSTEM DROP DATABASE REPLICA: -
A change for SYSTEM DROP DATABASE REPLICA: - When dropping with database or drop the whole replica: it also drops replica for each table of the database - If 'WITH TABLES' is provided, drop replica for each storage - Otherwise, the logic is unchanged, only drop replica on the databases - When dropping a database replica with the keeper path: - If 'WITH TABLES' is provided: - Restore the database as Atomic - Restore RMT tables from statement in Keeper - Drop the database (restored tables are also dropped) - Otherwise, only drop replica on the provided keeper path. #85637 (Tuan Pham Anh).
Why it matters
This feature allows more granular control when dropping a database replica by optionally dropping replicas for each table individually. It addresses the need to clean up replicas at the table level within a database, improving replica management and consistency especially when dealing with distributed or atomic databases with replicated tables.How to use it
Use theSYSTEM DROP DATABASE REPLICA command with the optional WITH TABLES keyword. Without WITH TABLES, only the database-level replica is dropped. With WITH TABLES, replicas for each table within the database are dropped as well. When dropping replicas with a keeper path and WITH TABLES is used, the database is restored as atomic, replicated tables are restored from Keeper statements, and then dropped along with the database.