Table Update Strategy

From: Paul Nader <Paul.Nader_at_d22mail.alcatel.com.au>
Date: Fri, 08 Jun 2001 09:25:13 +1000
Message-ID: <3B200D59.5C1F10C9@d22mail.alcatel.com.au>

Hi,

I have two tables A and A_Update. Both tables are identical in stucture down to the primary key.

The content of A_Update is replaced every so often by a run of the SQL Loader. These updates contain both rows already present in A (ie the primary keys match but the other columns may contain new values), and completely new rows (ie the primary key in A_Update is not present in A).

What is the best strategy for updating A based on A_Update such that the common rows are updated, new rows are inserted and disjoint rows are left unchanged?

Should I perform an insert from A_Update to A and then do an update of all rows or the other way round?

Are there better options?

Thanks in advance, Paul. Received on Thu Jun 07 2001 - 18:25:13 CDT