Support DESK

Follow

S4.10 - Deprecated Stored Procedures

Previous Article matchIT SQL Index Next Article 

4.10.1      msp_CreateKeysTable

WARNING: This stored procedure has been deprecated and will be removed in a future release of matchIT SQL.  The stored procedure should no longer be used – except for configurations that have compatibility setting less than 2.0.0 – and existing processes should be modified accordingly.

 

Input Parameters:

  • Configuration file – the file path of the configuration file to be used when this procedure is run.
  • Datasource ID – specifies the data source to be used within the configuration file, which contains the table and column mapping specifications.

 

 

Setting

Description

datasources

Specifies the database connection, table and column mappings used to define the dataset being processed.

The keys table that will be created when this procedure runs will have the same name as the first mapped table with a ‘__keys__’ suffix.

generalSettings->deleteKeysTableOnGenerate

When this setting is switched on, the keys table (if it already exists) will be deleted and recreated by this procedure, prior to being re-populated with keys by the BulkGenerateKeys stored procedure.

outputSettings->keyColumns

Specifies the columns that the keys table is created with (and populated by BulkGenerateKeys).

Note that all key fields used in the match keys (such as the fuzzy and exact match keys if running the relevant stored procedures) must be included in the keys table.

 

 

4.10.2      msp_AddKeyFieldsToTable

WARNING: This stored procedure has been deprecated and will be removed in a future release of matchIT SQL.  The stored procedure should no longer be used, and existing processes modified accordingly.

 

Input Parameters:

  • Configuration file – the file path of the configuration file to be used when this procedure is run.
  • Datasource ID – specifies the data source to be used within the configuration file, which contains the table and column mapping specifications.
  • Table name – specifies the named table that the key columns will be added to.

 

Simply appends all necessary matching and key fields to the specified table in the database (using the connection string specified in the datasource).

Note that to use this procedure, your XML must specify only one table in the datasources section, and this must also be marked as the keys table. 

e.g.

<tables>

  <table name="contacts" isKeysTable="true" />

</tables>

 

4.10.3      msp_GenerateKeys

WARNING: This stored procedure has been deprecated and will be removed in a future release of matchIT SQL.  The stored procedure should no longer be used, and existing processes modified accordingly.

 

Input Parameters:

  • Configuration file – the file path of the configuration file to be used when this procedure is run.
  • Datasource ID – specifies the data source to be used within the configuration file, which contains the table and column mapping specifications

 

This procedure generates the match key field values for all records in the current database (using the connection string specified in the datasource).

We highly recommended using msp_BulkGenerateKeys, with a separate keys table, as it provides the best key generation performance.                                                                                   

The settings are the same as msp_BulkGenerateKeys, except that the matching and key field data is not bulk loaded into an empty keys table. Significantly increasing the time taken for key generation, particularly when used with large databases.

 

4.10.4      msp_CreateCustomMatchesTable

WARNING: This stored procedure has been deprecated and will be removed in a future release of matchIT SQL.  The stored procedure should no longer be used, and existing processes modified accordingly.

 

Input Parameters:

  • Configuration file – the file path of the configuration file to be used when this procedure is run.
  • Datasource ID – specifies the data source to be used within the configuration file, which contains database connection string and table/column mappings.
  • Table name suffix – table in which to create the primary key column.

 

Creates a custom schema of a matches table from the standard matches table as defined in the configuration object for the specified data source.  Relies on a matches table existing in the specified data source.  The table name defined in the configuration can be given a suffix as the third parameter of the procedure if creating multiple instances to distinguish between them.

 

 

4.10.5     msp_CreateCustomGroupedMatchesTable

WARNING: This stored procedure has been deprecated and will be removed in a future release of matchIT SQL.  The stored procedure should no longer be used, and existing processes modified accordingly.

 

Input Parameters:

  • Configuration file – the file path of the configuration file to be used when this procedure is run.
  • Datasource ID – specifies the data source to be used within the configuration file, which contains database connection string and table/column mappings.
  • Table name suffix – table in which to create the primary key column.

 

Creates a custom schema of a grouped matches table from the standard matches_grouped table as defined in the configuration file for the specified data source.  Relies on a matches_grouped table existing in the specified data source.  The table name defined in the configuration can be given a suffix as the third parameter of the procedure if creating multiple instances to distinguish between them.

 

4.10.6      msp_GroupOverlap

 

Input Parameters:

  • Configuration file – the file path of the configuration file to be used when this procedure is run.
  • Datasource ID – specifies the data source to be used within the configuration file, which contains database connection string.
  • Level – Matching Level at which to group the records (Individual, Family, Household, Business, Custom).

 

After running msp_FindOverlap, this will group all matching record pairs into sets of matching records.  If you have previously run FindExactOverlap, then we recommend that you copy the matching pairs data from your exact_matches table into you matches table prior to running this grouping step, unless Merge Exact Matches is enabled.

 

Setting

Description

generalSettings->preventBridgedMatches

When enabled matchIT SQL will attempt to stop match groups containing bridged records such as:

J Smith

John Smith

Julian Smith

In the scenario above, both John Smith and Julian Smith match with J Smith, but not with each other.

generalSettings->masterRecordIdentification

When this setting is active, matchIT SQL will use the MasterPriority matrix to determine which record in a matching group should be marked as the master record (i.e. the best record). When this setting is off, the record with the lowest unique_reference will be chosen as the master record.

dataSources->ConnectionString

Connection string used to connect to the database during processing.

outputSettings->groupedMatchesTable

Name of the group matches output table that will be produced during the processing of this procedure.

Note that if the overlap attribute is empty, then the name in the name attribute will be used.

outputSettings->matchesTable

Name of the matches table containing the matching pairs that will be used as the input source for this procedure.

Note that if the overlap attribute is empty, then the name in the name attribute will be used.

 

 

4.7.2.2      Overlap matches_grouped table structure

During processing the stored procedure will output the results to the matches_grouped table (this name can be configured – see above). The structure of the output table is as follows:

 

Column

Description

ID

Record ID for each matching group.

Record1

Reference ID of the first record in the matching pair (from the Main database)

Record2

Reference ID of the record that is deemed to match Record1 From the Overlap datasource.

Score

The Score column is copied from the relevant level’s total score (grouping can only take place on one matching level; to group using multiple levels requires multiple runs of GroupMatches/GroupOverlap).

MatchRef

Indicates the unique reference of the master record in the group.

In the case of an overlap, the MatchRef column indicates the unique reference of the record from the overlap table; in effect, it’s a simple copy of the Record2 column.

BaseScore

Indicates the lowest score of all the matches in the group, normally not relevant to an overlap.

 

Previous Article matchIT SQL Index Next Article

 

Was this article helpful?
0 out of 0 found this helpful

0 Comments

Please sign in to leave a comment.