(wrong string) ünchen

rthomtxl_at_aol.com (Thomas) wrote in
news:ebd4de75.0302122353.3a3e8f12_at_posting.google.com:

> 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?

What about UPDATEs?
What about DELETEs? Received on Fri Feb 14 2003 - 03:11:08 CET