[dba-VB] Merge / Purge

John,

> >> wins" strategy. Every field in every record has to be examined. "Existing data" cannot 
be 
> >> overwritten by "no data" but MUST be overwritten by "most recent data". Recent is 
defined by record 
> >> position, NOT date (I don't have date info).

SQL Server doesn't have a concept of chronological record position. Unless there is 
atimestamp or incrementing field, there is no way to know which is the most recent entry or 
to guarantee that the most recent will be the "last" record in the recordset selected.

Do use have an incrementing key field?


Stuart McLachlan