Advanced Replication Guide : Updating and maintaining the schema of a distributed system : Managing solidDB® tables and databases : Unregistering a replica database
  
Unregistering a replica database
When a replica database is not used in a advanced replication system, it is strongly recommended that it is unregistered, i.e. the synchronization relationship between the replica and master databases is removed. After unregistering the replica, the master database knows that it does not need to accumulate synchronization history data for this replica database any more. This may save significant amounts of disk space in the master database.
To unregister a replica database:
1 Drop the subscription(s) in the replica if data is no longer needed in the replica database.
2 In the replica, use the following command to unregister the replica with the master database:
MESSAGE message_name BEGIN;
MESSAGE message_name APPEND UNREGISTER REPLICA;
MESSAGE message_name END;
COMMIT WORK;
3 Send the message to the master database.
MESSAGE message_name FORWARD TIMEOUT seconds;
COMMIT WORK;
The replica database can no longer synchronize with the master database.
A replica database can also be dropped from the master database using the following command in the master database:
DROP REPLICA replica_name;
If you drop the replica using DROP REPLICA, you should also drop the master from the replica with DROP MASTER.
This method may be necessary if access to the master database needs to be denied from the replica database or the replica database was not able to successfully unregister itself.
See also
Managing solidDB® tables and databases