MatchUp Object:Important - Revision history

Admin at 19:01, 1 May 2020

2020-05-01T19:01:23Z

@@ Line 1: / Line 1: @@
 [[MatchUp Object|&larr; MatchUp Object]]
 {{CustomTOC}}
 ==Notices (Build 5009)==
 ===MatchUp2017Q3 Update===

Admin at 20:55, 6 October 2017

2017-10-06T20:55:22Z

← Older revision		Revision as of 20:55, 6 October 2017
Line 1:		Line 1:
	[[MatchUp Object\|← MatchUp Object]]		[[MatchUp Object\|← MatchUp Object]]
	{{CustomTOC}}		{{CustomTOC}}
			==Notices (Build 5009)==
			===MatchUp2017Q3 Update===
			:The MatchUpSQL.dll was corrupted during the build process.

			:Download the patch here: ftp://ftp.melissadata.com/Updates/MatchUp2017Q3_v5009.1.zip

			:If using the SQL-CLR functions, Please stop the SQL service. Unzip. Rename the .d_l to .dll. Replace MatchUpSQL.dll in the SQL Server where you install the CLR functions. Restart the service.


	==Notices (Build 2929)==		==Notices (Build 2929)==
	If using the SQL-CLR functions, we recommend you rerun the ‘SQL-CLR install.sql’ script after stopping the service and replacing the mdMatchUp.dll and MatchUpSQL.dll libraries as instructed in the sample readme_SQL_CLR.txt.		If using the SQL-CLR functions, we recommend you rerun the ‘SQL-CLR install.sql’ script after stopping the service and replacing the mdMatchUp.dll and MatchUpSQL.dll libraries as instructed in the sample readme_SQL_CLR.txt.

Admin at 20:50, 9 March 2017

2017-03-09T20:50:13Z

← Older revision		Revision as of 20:50, 9 March 2017
Line 2:		Line 2:
	{{CustomTOC}}		{{CustomTOC}}
	==Notices (Build 2929)==		==Notices (Build 2929)==
	If using the SQL-CLR functions, we recommend you rerun the ‘SQL-CLR install.sql’ script after stopping the service and replacing the mdMatchUp.dll and MatchUpSQL.dll libraries as instructed in the sample readme_SQL_CLR.txt.		If using the SQL-CLR functions, we recommend you rerun the ‘SQL-CLR install.sql’ script after stopping the service and replacing the mdMatchUp.dll and MatchUpSQL.dll libraries as instructed in the sample readme_SQL_CLR.txt.

	Since Domestic and Global functionality have been separated into distinct downloads, the Global mdMatchUp.mc contains matchcodes used in its samples, which are not present in an existing previously installed MatchUp Object. Therefore, some of the Global examples will not run unless you swap in the new matchcode file, or add them to your existing .mc file (which is not overwritten upon a program update).		Since Domestic and Global functionality have been separated into distinct downloads, the Global mdMatchUp.mc contains matchcodes used in its samples, which are not present in an existing previously installed MatchUp Object. Therefore, some of the Global examples will not run unless you swap in the new matchcode file, or add them to your existing .mc file (which is not overwritten upon a program update).

Admin at 16:53, 9 March 2017

2017-03-09T16:53:06Z

← Older revision		Revision as of 16:53, 9 March 2017
Line 1:		Line 1:
	[[MatchUp Object\|← MatchUp Object]]		[[MatchUp Object\|← MatchUp Object]]
	{{CustomTOC}}		{{CustomTOC}}
			==Notices (Build 2929)==
			If using the SQL-CLR functions, we recommend you rerun the ‘SQL-CLR install.sql’ script after stopping the service and replacing the mdMatchUp.dll and MatchUpSQL.dll libraries as instructed in the sample readme_SQL_CLR.txt.
			Since Domestic and Global functionality have been separated into distinct downloads, the Global mdMatchUp.mc contains matchcodes used in its samples, which are not present in an existing previously installed MatchUp Object. Therefore, some of the Global examples will not run unless you swap in the new matchcode file, or add them to your existing .mc file (which is not overwritten upon a program update).


	==Notices (Build 2918)==		==Notices (Build 2918)==

Admin at 19:00, 3 February 2017

2017-02-03T19:00:11Z

← Older revision		Revision as of 19:00, 3 February 2017
Line 5:		Line 5:
	This version separates MatchUp Object into two distinct products - Global and Domestic (US and Canada).		This version separates MatchUp Object into two distinct products - Global and Domestic (US and Canada).
	All efforts have been made to ensure backwards compatibility, thus with the previous version, there are		All efforts have been made to ensure backwards compatibility, thus with the previous version, there are
	features (such as matchcode components and fuzzy ~~algorithms0~~ which appear in both versions.		features (such as matchcode components and fuzzy algorithms which appear in both versions.

	If performaing an update, we recommend backing up your mdMatchUp.mc matchcode file.		If performaing an update, we recommend backing up your mdMatchUp.mc matchcode file.

Admin at 18:02, 3 February 2017

2017-02-03T18:02:57Z

@@ Line 1: / Line 1: @@
 [[MatchUp Object|&larr; MatchUp Object]]
 {{CustomTOC}}
 ==Expired Database without Updates==

Admin at 18:36, 4 January 2016

2016-01-04T18:36:17Z

← Older revision		Revision as of 18:36, 4 January 2016
Line 12:		Line 12:
	This version marks a change in the way MatchUp handles International records for deduping. Melissa Data offers Global address verification and parsing for over 240 countries. MatchUp will now leverage this knowledge to enable us to recognize and build matchkeys for these countries, therefore providing accurate record matching across the globe.		This version marks a change in the way MatchUp handles International records for deduping. Melissa Data offers Global address verification and parsing for over 240 countries. MatchUp will now leverage this knowledge to enable us to recognize and build matchkeys for these countries, therefore providing accurate record matching across the globe.

	==Installation==		===Installation===
	We will no longer distribute 32 bit unmanaged libraries, nor 32 - 64 bit COM Objects. Migrating from these libraries to the 64 bit library or interface wrapper will require interface signature changes and a recompile of your project.		:We will no longer distribute 32 bit unmanaged libraries, nor 32 - 64 bit COM Objects. Migrating from these libraries to the 64 bit library or interface wrapper will require interface signature changes and a recompile of your project.

	==Domestic US and Canada==		===Domestic US and Canada===
	Same as it ever was.		:Same as it ever was.

	Previous versions provided unparalleled address parsing for keybuilding and deduping for domestic US and Canadian data. If your data is limited to these countries you should continue to use the same matching strategies in a seamless fashion		:Previous versions provided unparalleled address parsing for keybuilding and deduping for domestic US and Canadian data. If your data is limited to these countries you should continue to use the same matching strategies in a seamless fashion

	==Important for SSIS Users==		===Important for SSIS Users===
	The previous version of the MatchUp Object and the current SSIS component use the same data files. Since the SSIS component does not have Global Matching capability yet, its data files have a different structure. For both products to exist on the same machine, you must not point to the same location for the data files. MatchUp object, by default will install the data files to C:\ProgramData\Melissa DATA\MatchUP. Verify the location of your SSIS MatchUp data files – by selecting ‘File > Advanced Configuration’ from the component. If you did not override the default location, use windows explorer to navigate to that location and make a copy of that directory. Go into the component and point your SSIS data directory to the new location. Remove the contents of the original default directory. You can then install the MatchUp Object with Global capabilities.		:The previous version of the MatchUp Object and the current SSIS component use the same data files. Since the SSIS component does not have Global Matching capability yet, its data files have a different structure. For both products to exist on the same machine, you must not point to the same location for the data files. MatchUp object, by default will install the data files to C:\ProgramData\Melissa DATA\MatchUP. Verify the location of your SSIS MatchUp data files – by selecting ‘File > Advanced Configuration’ from the component. If you did not override the default location, use windows explorer to navigate to that location and make a copy of that directory. Go into the component and point your SSIS data directory to the new location. Remove the contents of the original default directory. You can then install the MatchUp Object with Global capabilities.

	We plan on adding Global matching to SSIS in the near future, which will then use the same data files.		:We plan on adding Global matching to SSIS in the near future, which will then use the same data files.

	==Important UK Changes==		===Important UK Changes===
	If you currently process UK data, or use a matchcode with UK components, DO NOT UPDATE to this version. Global UK processing will be added next release.		:If you currently process UK data, or use a matchcode with UK components, DO NOT UPDATE to this version. Global UK processing will be added next release.

	Next release: Global MatchUp will make the UK components obsolete, and therefore they will be deprecated. We have taken great effort to include logic to prevent Initialization of a process with these deprecated components. We recommend that you remove UK matchcodes and create new matchcodes which use the respective new global components.		:Next release: Global MatchUp will make the UK components obsolete, and therefore they will be deprecated. We have taken great effort to include logic to prevent Initialization of a process with these deprecated components. We recommend that you remove UK matchcodes and create new matchcodes which use the respective new global components.

	==General International Usage==		===General International Usage===
	Supported Countries – Build 2618: Germany		:Supported Countries – Build 2618: Germany

	As suggested for UK, we have provided a new set of Global matchcode components which will allow you to match international addresses with custom matchcodes based on a countries’ individual format, which differs from country to country. This will require you to know the expected address components needed to uniquely identify one particular address from another. Seem hard? It’s actually not as random in differences as you might think, and Melissa Data will allows offer sound advice as to which strategy and components to use for your particular need.		:As suggested for UK, we have provided a new set of Global matchcode components which will allow you to match international addresses with custom matchcodes based on a countries’ individual format, which differs from country to country. This will require you to know the expected address components needed to uniquely identify one particular address from another. Seem hard? It’s actually not as random in differences as you might think, and Melissa Data will allows offer sound advice as to which strategy and components to use for your particular need.

	For MatchUps’ international address parser / key builder to kick in, the first matchcode component will need to be of the datatype Country. This will tell MatchUp to look for specific keywords and address patterns for that country.		:For MatchUps’ international address parser / key builder to kick in, the first matchcode component will need to be of the datatype Country. This will tell MatchUp to look for specific keywords and address patterns for that country.

	In addition to varying address formats, your international records will most likely have an extended character set. Therefore, you will need to call the new SetEncoding and SetCharacterSize methods. This lets MatchUp know how to recognize different characters and correctly build the matchkeys. Previously, all extended characters were converted for keybuilding with the default 1252 code page. This allowed Matchup to identify matches whether or not records were stripped of their accents by legacy data systems. With Global data, this is not desired as differently accented characters do represent different data values.		:In addition to varying address formats, your international records will most likely have an extended character set. Therefore, you will need to call the new SetEncoding and SetCharacterSize methods. This lets MatchUp know how to recognize different characters and correctly build the matchkeys. Previously, all extended characters were converted for keybuilding with the default 1252 code page. This allowed Matchup to identify matches whether or not records were stripped of their accents by legacy data systems. With Global data, this is not desired as differently accented characters do represent different data values.

	==International Datafiles==		===International Datafiles===
	To accommodate global processing, the structure and contents of the underlying Matchup database – mdMatchup.dat has changed. There are also a significant number of new and larger required data files which will be installed and required to process international records.		:To accommodate global processing, the structure and contents of the underlying Matchup database – mdMatchup.dat has changed. There are also a significant number of new and larger required data files which will be installed and required to process international records.

	==Backwards Compatibility==		===Backwards Compatibility===
	MatchUp is backwards compatible. Updating to the newest library should not break an existing process. Though we have taken great effort to include logic to handle Initialization of a process with the deprecated components, there may be subtle differences in the way that matchkeys are constructed. This is too accommodate extended characters, plural words and an overall general improvement to the existing data files. We therefore recommend you generate new matchkeys for any existing Incremental or Hybrid process, or run thorough regression tests before updating the libraries to your production environment.		:MatchUp is backwards compatible. Updating to the newest library should not break an existing process. Though we have taken great effort to include logic to handle Initialization of a process with the deprecated components, there may be subtle differences in the way that matchkeys are constructed. This is too accommodate extended characters, plural words and an overall general improvement to the existing data files. We therefore recommend you generate new matchkeys for any existing Incremental or Hybrid process, or run thorough regression tests before updating the libraries to your production environment.


	[[Category:Issues]]		[[Category:Issues]]
	[[Category:MatchUp Object]]		[[Category:MatchUp Object]]

Admin at 21:35, 30 December 2015

2015-12-30T21:35:54Z

← Older revision		Revision as of 21:35, 30 December 2015
Line 1:		Line 1:
	[[MatchUp Object\|← MatchUp Object]]		[[MatchUp Object\|← MatchUp Object]]
	{{CustomTOC}}		{{CustomTOC}}

			==Expired Database without Updates==
			Users who do not update to MatchUp build 2628 will experience an expired database (actual expiration date is 2015-12-29).

			Updating to build 2628 (or newer future builds) will enable Global Matching for supported Countries but may require changes to your application (see [[Build History:MatchUp Object\|build history]]), and are not effected by an expiring database date.

			Users who do not update and need an mdMatchUp.dat with an extended expiration date, please contact our tech support team at tech@melissadata.com or 1-800-800-6245 x4.

	==Notices (Build 2628)==		==Notices (Build 2628)==

Admin: Created page with "← MatchUp Object {{CustomTOC}} ==Notices (Build 2628)== This version marks a change in the way MatchUp handles International records for deduping. Mel..."

2015-08-21T21:08:33Z

Created page with "← MatchUp Object {{CustomTOC}} ==Notices (Build 2628)== This version marks a change in the way MatchUp handles International records for deduping. Mel..."

New page

[[MatchUp Object|← MatchUp Object]]
{{CustomTOC}}

==Notices (Build 2628)==
This version marks a change in the way MatchUp handles International records for deduping. Melissa Data offers Global address verification and parsing for over 240 countries. MatchUp will now leverage this knowledge to enable us to recognize and build matchkeys for these countries, therefore providing accurate record matching across the globe.

==Installation==
We will no longer distribute 32 bit unmanaged libraries, nor 32 - 64 bit COM Objects. Migrating from these libraries to the 64 bit library or interface wrapper will require interface signature changes and a recompile of your project.

==Domestic US and Canada==
Same as it ever was.

Previous versions provided unparalleled address parsing for keybuilding and deduping for domestic US and Canadian data. If your data is limited to these countries you should continue to use the same matching strategies in a seamless fashion

==Important for SSIS Users==
The previous version of the MatchUp Object and the current SSIS component use the same data files. Since the SSIS component does not have Global Matching capability yet, its data files have a different structure. For both products to exist on the same machine, you must not point to the same location for the data files. MatchUp object, by default will install the data files to C:\ProgramData\Melissa DATA\MatchUP. Verify the location of your SSIS MatchUp data files – by selecting ‘File > Advanced Configuration’ from the component. If you did not override the default location, use windows explorer to navigate to that location and make a copy of that directory. Go into the component and point your SSIS data directory to the new location. Remove the contents of the original default directory. You can then install the MatchUp Object with Global capabilities.

We plan on adding Global matching to SSIS in the near future, which will then use the same data files.

==Important UK Changes==
If you currently process UK data, or use a matchcode with UK components, DO NOT UPDATE to this version. Global UK processing will be added next release.

Next release: Global MatchUp will make the UK components obsolete, and therefore they will be deprecated. We have taken great effort to include logic to prevent Initialization of a process with these deprecated components. We recommend that you remove UK matchcodes and create new matchcodes which use the respective new global components.

==General International Usage==
Supported Countries – Build 2618: Germany

As suggested for UK, we have provided a new set of Global matchcode components which will allow you to match international addresses with custom matchcodes based on a countries’ individual format, which differs from country to country. This will require you to know the expected address components needed to uniquely identify one particular address from another. Seem hard? It’s actually not as random in differences as you might think, and Melissa Data will allows offer sound advice as to which strategy and components to use for your particular need.

For MatchUps’ international address parser / key builder to kick in, the first matchcode component will need to be of the datatype Country. This will tell MatchUp to look for specific keywords and address patterns for that country.

In addition to varying address formats, your international records will most likely have an extended character set. Therefore, you will need to call the new SetEncoding and SetCharacterSize methods. This lets MatchUp know how to recognize different characters and correctly build the matchkeys. Previously, all extended characters were converted for keybuilding with the default 1252 code page. This allowed Matchup to identify matches whether or not records were stripped of their accents by legacy data systems. With Global data, this is not desired as differently accented characters do represent different data values.

==International Datafiles==
To accommodate global processing, the structure and contents of the underlying Matchup database – mdMatchup.dat has changed. There are also a significant number of new and larger required data files which will be installed and required to process international records.

==Backwards Compatibility==
MatchUp is backwards compatible. Updating to the newest library should not break an existing process. Though we have taken great effort to include logic to handle Initialization of a process with the deprecated components, there may be subtle differences in the way that matchkeys are constructed. This is too accommodate extended characters, plural words and an overall general improvement to the existing data files. We therefore recommend you generate new matchkeys for any existing Incremental or Hybrid process, or run thorough regression tests before updating the libraries to your production environment.

[[Category:Issues]]
[[Category:MatchUp Object]]