| Title: | The Replication Option for Rdb |
| Notice: | Product renamed to Replication Option for Rdb |
| Moderator: | BROKE::PROTEAU |
| Created: | Wed Mar 02 1994 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 287 |
| Total number of notes: | 1231 |
Is it possible to set up a transfer that will transfer INSERT and
UPDATE activity, but not DELETE activity?
Background: A customer wants to have a production database with
only current data, and a data warehouse database with all the
old (archived) data and the current data. All current data will
be entered in the production database.
Diane
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 220.1 | Yes, we can perform "archive" transfers | BROKE::PROTEAU | Jean-Claude Proteau | Thu Jun 13 1996 10:11 | 17 |
Diane,
Yes, we can do what your customer wants, provided that the source
database is Oracle Rdb and the target database is either Oracle Rdb or
Oracle Rdbms.
To create such an "archive" transfer, use the following SQL syntax:
CREATE TRANSFER name-of-transfer TYPE IS REPLICATION WITH NO DELETE
...
When a row of data is deleted from a souce table, that change is
replicated to the target table. However, we do not delete the target
row. Instead, the deletion is marked in a special column added to the
target table, the DDAL$DBKEY column.
Claude
| |||||
| 220.2 | We might do "archiving" for other systems too | BROKE::PROTEAU | Jean-Claude Proteau | Wed Jul 24 1996 08:55 | 7 |
We are looking at the possibility of extending this "archiving"
capability to non-Oracle target systems, such as, MS SQL Server.
Right now, the implementation we use will not work because of the way
we mark target rows as having been deleted in the source. We have a
possible solution, but I don't know if we'll have time to investigate
it for inclusion in ROR 7.0.
| |||||