Search results

• Matchcode Optimization:UTF8 Near
  ===Example Matchcode Component=== ...an existing large master database. Batch level runs where other matchcode components are set to exact or databases of a single country origin.
  2 KB (210 words) - 14:32, 27 September 2018
• Contact Zone:Installation
  The License Key may be inserted during the Setup process for all purchased components, or individually, upon first use of each component. ===MatchUp Data, MatchCode, etc. files===
  1 KB (161 words) - 00:33, 3 January 2017
• MatchUp Object:Best Practices
  ...t show the problem. For more info: [[MatchUp Object:Matchcode Combinations|Matchcode Combinations]]. ...trategies. Given the quality of data and amount of records, use of certain matchcode properties may be impractical to achieve desired speeds.
  6 KB (879 words) - 20:17, 25 May 2018
• MatchUp Object:Matchcode:Order of Operations
  ...here are many options that must be considered for matchcodes and matchcode components. These are the basic steps of a typical implementation of the Matchcode interface.
  11 KB (1,507 words) - 21:57, 19 December 2016
• MatchUp Object:Matchcode Editor:Interface
  ...lected Matchcode; and a description of the Matching Rules for the selected matchcode. ==Matchcode Name==
  9 KB (1,468 words) - 18:18, 8 April 2022
• Contact Zone:MatchUp Tutorial
  Navigate to Tools > Melissa Data Settings > Components > MatchUp ===Matchcode Tab===
  3 KB (423 words) - 00:26, 5 January 2017
• MatchUp Object:Optimizing Matchcodes
  ...eed. 58-hour runs have been reduced to four hours simply by optimizing the matchcode. ...chcode works in the intended way before attempting any optimizations. If a matchcode is not functioning properly these optimizations will not help and could qui
  7 KB (1,015 words) - 18:53, 23 July 2015
• SSIS:MatchUp:Matchcodes:Optimization
  ...g the Optimize button in the Matchcode Editor will sufficiently optimize a matchcode. This discussion is included so developers can better understand why certai ...eed. 58-hour runs have been reduced to four hours simply by optimizing the matchcode.
  7 KB (1,045 words) - 20:33, 25 May 2018
• Pentaho:FAQ
  [[Data Quality Components for Pentaho|← Data Quality Components for Pentaho]] You can manually install the components into Pentaho simply by copying the desired Melissa Data zip archive and ext
  6 KB (913 words) - 22:16, 19 December 2016
• MatchUp Object:Introduction
  ...Street # + Street Name + ZIP Code™}, while another combination in the same matchcode would substitute PO Box™ for Street # and Street Name. With these options ...very sophisticated tool. If record 1 and 3 match with combination #1 in a matchcode, and record 2 and 3 match using combination #2- MatchUp Object will use inf
  3 KB (476 words) - 19:33, 21 July 2015
• MatchUp Object:Global Processing
  components. The Postal code component is structured in the following format: Like any other matchcode component, a portion of the Postal code can always be
  4 KB (566 words) - 19:28, 4 January 2019
• MatchUp Object:Matchcodes
  ...er when determining if two records are duplicates. MatchUp Object uses the matchcode to construct a “match key,” a simplified string of characters that repr ==Matchcode Components==
  8 KB (1,184 words) - 22:19, 5 August 2015
• MatchUp Object:Matchcode:Change Settings
  ...ey can be used to construct new matchcode components when adding them to a matchcode, or to change the settings of an existing component. Every function in this ...ese enumerations, see [[MatchUp Object:Enumerations#MatchcodeComponentType|Matchcode Component Type Enumerations]].
  11 KB (1,436 words) - 00:19, 9 April 2022
• SSIS:Best Practices
  [[SSIS:Data Quality Components|← SSIS:Data Quality Components]] ...ted functionality. Melissa data provides many ways to ensure you keep your components to the latest version.
  6 KB (960 words) - 23:19, 18 November 2019
• Issues:MatchUp Object
  The MatchUpEditor.exe standalone matchcode editor GUI interface will display an unhandled exception error when selecti ==Matchcode Component using Start:Word:1==
  4 KB (621 words) - 21:55, 11 January 2024
• MatchUp Object:Matchcode:Read Settings
  The following functions read and return the settings from a specific matchcode component variable. ...ese enumerations, see [[MatchUp Object:Enumerations#MatchcodeComponentType|Matchcode Component Type Enumerations]].
  9 KB (1,246 words) - 00:12, 8 August 2015
• MatchUp Object:Matchcode Components
  ==Matchcode Components== The following table lists all of the available matchcode components (Data Types) in
  7 KB (1,041 words) - 20:27, 1 June 2018
• Contact Zone:MatchUp:Matchcodes
  ...between two records. A match found using any one of the combinations in a matchcode is considered a match. Programmers may think in terms of a series of OR con MatchUp allows up to 16 different combinations of components per matchcode.
  20 KB (3,075 words) - 00:32, 5 January 2017
• Pentaho:MatchUp:Matchcodes
  ...between two records. A match found using any one of the combinations in a matchcode is considered a match. Programmers may think in terms of a series of OR con MatchUp allows up to 16 different combinations of components per matchcode.
  19 KB (2,918 words) - 22:06, 15 June 2015
• Pentaho/Contact Zone:MatchUp:Matchcodes
  ...between two records. A match found using any one of the combinations in a matchcode is considered a match. Programmers may think in terms of a series of OR con MatchUp allows up to 16 different combinations of components per matchcode.
  19 KB (2,924 words) - 20:49, 11 January 2017

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)