Page 2 of 2

Re: tables comparsion

PostPosted: Sat Jan 05, 2013 2:38 am
by dick scherrer
Hello,

but I want to do without unloading...
As the Rolling Stones said many years ago, "You can't always get what you want" . . .

Why do you even want this? Why not use the tools already available and do the unload / compare?

Is there some business or technical reason to use something other than the standard utilities that are part of the DB2 product?

Re: tables comparsion

PostPosted: Sat Jan 05, 2013 3:07 am
by enrico-sorichetti
what happened when You googled for
db2 compare databases

or
db2 compare tables

:mrgreen:

we are just wasting time on a TS unwilling to do the tiniest research by himself

Re: tables comparsion

PostPosted: Sat Jan 05, 2013 3:18 am
by Pedro
How about:
SELECT * FROM myschema.mytable1;   

while allocating SYSPRINT to a dataset.

Do the same for the second table then compare the two SYSPRINT datasets with SUPERC.

Of course, your test data should not be too simple. Most likely, your vendor will have tested simple things. You need to test to the length limits of LOB and XML columns, and so on.