Generic Data Reconciliation
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
I've moved on from that client since then. From memory, 3(a) was simply SELECT COUNT(*) FROM TABLE for both source and target, add artificial key ('X'), join and compare.
3(b) was very similar only it was SELECT * FROM TABLE ORDER BY keycolumn (with RCP enabled) and run through Checksum stages before the remainder. To be generic the SQL was built in an upstream server job that queried the system tables to get they key column name(s), and was then passed as a parameter to the comparison job.
3(b) was very similar only it was SELECT * FROM TABLE ORDER BY keycolumn (with RCP enabled) and run through Checksum stages before the remainder. To be generic the SQL was built in an upstream server job that queried the system tables to get they key column name(s), and was then passed as a parameter to the comparison job.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.