S4.4.2 - msp_FindExactOverlap

Lauren Wheeler

Input Parameters:

Configuration file – the file path of the configuration file to be used when this procedure is run.
Main datasource ID – specifies the data source to be used from the configuration file, which contains the table and column mapping specifications of the first dataset.
Overlap datasource ID – specifies the data source to be used from the configuration file, which contains the table and column mapping specifications of the second dataset to be used in the overlap.

Finds all records that exactly overlap the specified tables.

The ‘excludeExactMatches’ configuration option can be used with this stored procedure, as per msp_FindExactMatches.

Setting	Description
matchKeys->exactKeys	The match keys that will be used are specified in the XML within the exactKeys keys tags under the match keys section. Fields can be concatenated together to create an exact match key e.g. <key key1="mkName1" key2="mkName2" /> Which means that all records with the same phonetic forename and surnames will be recorded as matches.
dataSources	Defines the database connection, tables, and columns of the datasets that are to be matched.
outputSettings->exactMatchesTable	The Overlap attribute specifies the name of the exact_matches table that will be produced (which contains the results from the FindExactMatches processing). If the Overlap attribute is empty, the table will be given the same name as that specified in the name attribute.
outputSettings->reports	Specifies whether reporting is enabled, what folder the reports will be produced into, and what report format should be used.

During processing, exact matches are written to an overlap exact_ matches output table as configured within the configuration file used.

Column	Description
ID	Record ID for each matching pair.
Record1	Reference ID of the first record in the matching pair.
Record2	Reference ID of the record in the second supplied datasource that record1 has matched to.