I was able to create the script I was looking for under the same ideas that where mentioned... However due to the fact that I needed to work with Oracle Exports and Other variations of db links, we choose to use a working db to handle most of the data manipulation..
Based on that experience I just wanted to mention to everyone that if you tackle this problem ensure that all the data you are comparing is populated. At least in Oracle anyway, a null value cannot be compared to anything including another null value. So if you don't populate that field, you'll have missing data.
Another point I want to convey, is if you do happen to use a DB approach versus a hash/array/or whatever combination there of you will need to make sure you create indexes on these working tables you are working with. Otherwise the wait will be quite painful.
CHEERS
pdt1630
In reply to Re: Re: Full DB Table Compare
by pdt1630
in thread Full DB Table Compare
by pdt1630
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |