(wrong string) ünchen

Thomas wrote:
> I have one production database and one identical database (structure)
> on a different network.
>
> Each night, I need track the changes (insertions) that have taken
> place on the production database and then affect them on the offline
> system. Note that content of the online system that is old gets
> deleted whereas on the offline system, it sticks around forever: I am
> just tracking the inserts.
>
> exporting the database to a file would be a possibility if it checked
> changes at the row level as opposed to the table level. But since it
> doesn't and besides the output won't contain all the old deleted
> stuff, export is not an option.
>
> Is there a clever way to use archive logs or *whatever* to simply get
> a file containing insert statements that can be ftp'd over to the
> offline system?

Check out the Replication Mnl. You may be able to tweak the full master/snapshot replication in not doing deletes (you should check the triggers generated after 'Generate Replication Support'), or go for procedural replication.

Another option would be to replicate (a) local table(s), that holds inserts/updates of the production table(s). Replication is quite efficient, and does not need (a lot of ) maintenance, once set up.

-- 
Regards, Frank van Bortel