Compare Table Data - Primary Key required?

[Stew Stryker]

I know proper database design says that all good tables should have a primary key, but we don't always get to choose our database designs.

I'm trying to compare a table across multiple database instances, but it doesn't have a primary key. So when I try to compare it, PSD removes that table from the selection set, though it does have a unique index identified. But this is a table provided by a vendor, so we try to not change them unless absolutely required.

I'd like to request an enhancement that this PK restriction be removed, or at least relaxed so that a unique index will suffice in lieu of a primary key.

Thanks,

Stew

 

[Marco Kalter]

The compare function needs to be able to uniquely identify a record. A unique key instead of a primary key should be sufficient though, so I have added this to the list of enhancement requests.

 

[Gustavo]

Hi, Marco,

It's been 12 years since I last used this function. I was only able to use it before I started to work with Oracle eBusiness Suite (there are no PK defined, only Unique Indexes). I really miss this a lot. It used to be quite useful. ;-)

Regards,
Gustavo

 

[Amy]

Marco,

Has this enhancement been made? If not, how do you suggest we compare table data when there is no primary key?

Peace,
Amy

 

[Maxmix]

how do you suggest we compare table data when there is no primary key?

Or, if tables have LOB columns
Or, if tables have different names (for example, 2 tables reside in the same schema on same db).

I could use a visual comparison (along with sync script), when I choose databases, tables, columns, where clauses (this would allow compare
records even from the single table, filtered differently).

Am I too greedy? :grin: