Dave,

If it were me, I'd look at creating a new table with the identity column that Elvis provided a link
to.

Then, copy the data from the current PF to the new table and delete the existing PF. Now, create a
view or logical file with the same name that the original table had along with the same format, ie.
Without the new identity column.

You'd also need to recreate any existing logicals to point to the new physical.

However, when done properly, you won't need to recompile any vendor programs and the vendor
application should continue as if nothing has changed.

HTH,

Charles Wilt
--
Software Engineer
CINTAS Corporation - IT 92B
513.701.1307

wiltc@xxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Dave Odom
Sent: Wednesday, May 28, 2008 6:51 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Best way to make a table of non-unique rows, unique?

Gang,

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


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.




This e-mail transmission contains information that is intended to be confidential and privileged. If you receive this e-mail and you are not a named addressee you are hereby notified that you are not authorized to read, print, retain, copy or disseminate this communication without the consent of the sender and that doing so is prohibited and may be unlawful. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please delete and otherwise erase it and any attachments from your computer system. Your assistance in correcting this error is appreciated.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

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.