I've seen the other responses, but let me add one more.   The
advantage of this one is that you don't need to know the column
structure so if you change things later on you don't have to redo
your code.  You need "eqnull on" in the case of nulls in the coulmns,
otherwise nulls won't match

SET EQNULL ON
PROJECT temptable FROM yourtable USING ALL WHERE ....
APPEND yourview TO temptable WHERE.....
DELETE DUPLICATES FROM temptable

If no rows in the TempTable, then they all matched!

Karen
 
> Does anyone know of a means to compare two records, in toto, for 
> equality||inequality?
> 
> The records have exactly the same structure, including column names and 
> PK, and have a 1:1 relationship.
> 
> One record comes from a local table and represents the data as it was at 
> its original INSERTion or most recent UPDATE.  The other record is in a 
> view, populated by the data as it currently exists in a production database.  
> It might or might not have changed since the most recent refresh of the 
> local data.
> 
> I would like to find a way to take a "management by exception" approach to 
> by means of a record-by-record comparison between the pair of records.  
> Then, if there is a difference, dig into the nature of the inequality.
> 
> IOW, for any PK, is #RecordInLocalTable = #RecordInProductionView?  If 
> equal, get next PK-matched pair of records.  If not, then lather, rinse, 
> repeat.
> 
> Thanks,
> Steve in Memphis

Reply via email to