Could track Insert/Update date timestamps and query based on that.

Would probably have to track last time processed though, so probably not entirely bulletproof unless you also store a pointer somewhere that tells you a particular record was processed.

Maybe assigning a GUID would help and then writing that to the processed table.

Just some random thoughts at lunch time :-)

Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site: http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
------------------------------

message: 5
date: Tue, 1 May 2012 09:31:11 +0300
from: Gad Miron <gadmiron@xxxxxxxxx>
subject: Unique ID

Hello guys

Need some help with uniquely identifying records in data files that are
routinely extracted
to an external (SQL Server) data warehouse.

Only new or updated records are extracted and I need a way to tell which
record is new
(and add it to the DW) and which is existing updated record (in which case
update the existing record in the DW)

The transaction files are about 80 - 100 million records (all in all)

Since I could find a field combination that uniquely identify each records
I tries RRN but apparently some records gets deleted and it is no good.

Any help will be greatly appreciated

Gad


This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].