ALTER REPLICATION
DROP REPLICATE
Drops a
remote table from an existing table replication.
SYNTAX
| replication_name |
Name
of the synchronous table replication you want to drop a remote table
from. |
| local_table_name |
Name
of the local table the existing replication was created on. |
| remote_table_name |
Name
of the table in the remote database you want to stop replicating to. |
DESCRIPTION
The ALTER
REPLICATION DROP REPLICATE command drops a remote table from an existing
synchronous table replication. You can drop a remote table from a synchronous
table replication when you no longer want to replicate data to that table.
To execute the ALTER REPLICATION DROP REPLICATE command you must be the
table owner, or have DBA or SYSADM security privileges.
A table
replication creates a full or partial copy of a table in a remote location.
This allows users in remote locations to work with a local copy of data.
The local copy remains synchronized with the databases in other locations.
This way each database can service data requests immediately and efficiently,
without having to go to another machine over a slower network connection.
This is not the same as backing up the database to a remote location,
since the synchronization is done on a transaction-by-transaction basis
by the DBMS itself, without any intervention from users.
There are
two primary types of table replication: synchronous and asynchronous.
Synchronous table replication modifies the remote table at the same time
it modifies the local table, while asynchronous table replication stores
changes to the local table and modifies the remote table based on a schedule.
The ALTER REPLICATION DROP REPLICATE command modifies synchronous table
replications.
Synchronous
table replication in DBMaker uses a global transaction model, in which
the replication of data to the remote table is treated as an integral
part of the local transaction. (A transaction is traditionally defined
as a logical unit of work, or one or more operations on a database that
must be completed together to leave the database in a consistent state.
Transactions
are self-contained an must either complete and change the data, or fail
and leave the data unchanged.) This means that if the replication of data
to the remote database fails, the transaction on the local table will
also fail.
When you
modify a synchronous table replication you must specify the replication
name, the local table name, and the name of the remote table you want
to drop. You can drop more than one remote table on a synchronous table
replication by listing all tables you want to drop. Any replications you
create on a table are dropped automatically if you drop the table.
EXAMPLES
The following
example drops a remote table named Div1Emp from the replication named
EmpRep created on the local Employees table.
ALTER REPLICATION EmpRep ON Employees DROP REPLICATE TO Div1Emp
|
The following
example drops the remote tables named Div2Emp, Div3Emp, and Div4Emp from
the replication named EmpRep created on the local Employees table.
ALTER REPLICATION EmpRep ON Employees
DROP REPLICATE TO Div2Emp, Div3Emp, Div4Emp
|
RELATED COMMANDS
<
ALTER REPLICATION ADD REPLICATE
| Contents | ALTER
TABLE ADD COLUMN >
|
