Page History

...

Primary Keys tell Aqua Data Studio against which rows to perform a match. When you compare result sets, the common column headers in both result sets are primary keys. In the following example, after applying primary keys on the Total Medals column, Results Compare matched the unique records for Total Medals and displayed the contents of the matched records as identical or not. Also, see Comparison Results Scenarios. 

Limitations: If a query returns multiple rows with the same primary keys, then there is no reliable way to identify modified rows in the result sets. Multiple rows of the same primary keys are obtained in 2 cases: due to user selection of the primary keys and the selection of the query columns. Initially, Results Compare is run with all of the common columns selected as primary keys. Here, if the query returns duplicate rows, it is due to query column selection. If a table has duplicate rows and no primary key defined, then there is no way to determine if those rows have been modified even though a user selects all of the table columns for the query and all of the common columns as primary keys. If this problem occurs, Results Compare is still run on the result sets using intelligent assumptions about what rows correspond to each other, but a user is warned about duplicate rows. If there are duplicate rows in the result sets on the initial run, then a user is advised to change column selection in the query. If there are duplicate rows obtained after a user changes the set of primary keys, then the user is advised to redefine the primary keys.

...