×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I have some tables from a vendor using OLD, OLD, OLD, non-relational architecture which allows duplicate rows. I need to find a way to make the rows in these tables capable of having uniqueness for a unique key, even it the rows are "copied" and kept updated to like-type tables.
Since I can't touch the original tables because they are from a vendors app., I was thinking of copying the rows in the original tables to new tables with an added column wherein I could put something like a datatimestamp to make the row unique. I'd like to use something at the database level like a trigger or stored procedure but, if necessary, I'll write an old fashion program to do the work.
The reason for all this is that I'm using DataPropagator to map and keep in sync tables in a data warehouse in a separate LPAR and DataPropagator has to build a unique key over the target tables based on whatever makes rows unique in the source tables. Well, if the source tables have duplicates, I have to find a way around that or DataPropagator won't work for the last 11 tables I have to map/keep in sync.
Thanks in advance,
David Odom
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.