Melissa Data Wiki - User contributions [en]

FAQ:SSIS:Known Issues

2014-03-05T19:19:17Z

Joseph:

__FORCETOC__
==SSIS: Matchup - Date Keys are Not Being Built Correctly==
:When using the Component Type: Date in your MatchCode, Date Keys sometimes do not get built in the MatchKey. This is due to a conflict in the expected input format for Dates. Date Inputs should be in the format 'yyyMMdd'. This becomes problematic particularly for some DBMS. SQL Server for example may have a Date Column defined with char[30]. This causes trailing spaces to be included in the Date Input which conflicts with the expected Input Format, causing the Date Key to not be built.

:;Future Resolution
:We will be adding a fix in a later build to trim the trailing white spaces for Date Inputs.

[[Category:Known Issues]]
[[Category:SSIS:Data Quality Components]]

FAQ:SSIS:Data Quality Components

2014-03-05T19:18:40Z

Joseph:

__FORCETOC__
==Can we save current settings for DQC for future?==
;Answer:
:Yes, Melissa Data SSIS includes the feature that you can save currents settings for future use. Under File Tab you can save current setting in a .cfg file in local your drive. Under same File tab click "Open" and upload the .cfg file.

==Speed Facts for CVC?==
;Answer:
:EVC is an enterprise component so performance of EVC is highly dependent on machine configuration. Operating System, RAM, Processor or using network drive for data input or output, make significant impact on performance of EVC. In addition performance also depends upon 2 more main factors:

===How you are using EVC?===
:;Answer:
::It is highly recommended for EVC users, select the only those features i.e. LACSLink(Address Add-on) DNS Lookup(Email, Add-on), which are required. Unnecessary use of add-on and feature will effect the performance.

===Type of Data?===
:;Answer:
::If the input data is really corrupted or having lot of errors, will effect the performance.

We have additional 2 different scenarios for using EVC, which will help you to analyse the throughput of the component in different situations. For more information you can click on following link:
[http://www.melissadata.com/ssis1/SSIS-Speed-Scenarios.pdf SSIS Speed Scenarios]

==In which format Data Quality Components(DQC) accept input?==
;Answer:
:You can use any format as input for Melissa Data SSIS components. It can be .csv, .xls, .dbf, xlsx, SQL database etc. In some cases you might not see any column in drop down options of MD SSIS component, in this case you can use "Data Conversion"(in-built component in BIDS) to change the data type of particular missing column to "DT_WSTR".

==How we can update individual Melissa Data Object rather than updating whole CVC?==
;Answer:
:EVC component installs all Melissa Data Objects in "Binn" folder under DTS folder of SQL Server. If you are using EVC in SQL Server 2008 and need to update only Address Object grab latest mdAddr.dll and replace older mdAddr.dll in following location:
<blockquote>
<pre>C:\\Program Files\\Microsoft SQL Server\\100\\DTS\\PipelineComponents</pre>
</blockquote>
:Same way you can update other Melissa Data Objects i.e for Email Object replace mdEmail.dll, for GeoCoder mdGeo.dll, etc.

:;Note:
::If you are installed EVC on SQL Server 2005, the location of Melissa Data Object will be in following location:
<blockquote>
<pre>C:\\Program Files\\Microsoft SQL Server\\90\\DTS\\PipelineComponents</pre>
</blockquote>

==Microsoft Fuzzy Lookup vs. The Data Matching and Cleansing Component?==
;Answer:
:The Microsoft transforms are only available with SQL Server enterprise edition which is a significant cost in itself if your organization doesn’t have it already.
:All of the following transforms are SQL Server Enterprise edition only:
:*Data Mining Training Destination
:*Data Mining Query Component
:*Fuzzy Grouping
:*Fuzzy Lookup
:*Term Extraction
:*Term Lookup
:*Dimension Processing Destination
:*Partition Processing Destination

The MD Fuzzy Matching Component allows more granular control over matching whereas the SSIS native fuzzy matching does not allow any control of its algorithms or access to multiple algorithms. There are only two configurable parameters with the stock Fuzzy lookup and grouping components ie: similarity threshold and maximum number of results per input record.

The MD Fuzzy Matching component has 16 configurable matching algorithms some of them developed specifically by us such as the unique Keyboard distance for misspellings. All industry standard matching algorithms are supported, and probabilistic match settings can be configured for each column of data and the rules can be daisy chained for maximum catch all situations. Also the component has the ability to ignore common data quality issues when matching. ie; whitespaces, irregular characters, etc.

The Melissa Data Fuzzy Matching Component can also inherently cleanse your data through regular expressions. Regular expressions can be built and tested through an expression builder which is also built in to the component. Cleansing your data prior to matching is a crucial step in order to get the most accurate results for matching.

The component also is able to automatically split up the results into 3 destinations: Matches, Possible Matches and Non-Matches. Based off the percentage score between 2 records, the component will re-direct the results to the appropriate destination according to the percent thresholds you’ve set in the component. Also the Fuzzy SSIS component has full metadata (source and compare scores for multiple algorithms) for tracking record lineages.

One more thing to bear in mind is that, the stock Fuzzy Lookup component in SSIS requires that your reference table be a SQL Table. The Fuzzy Matching Component does not limit you to a SQL Table Reference Database.

The DMCC suite also comes with the MatchUP component, which is specially designed for the unique set of matching problems with Address, Name and Company data fields. MatchUp recognizes combinations, inverse names, Acronyms, Nick names, numerical streets such as 12th vs. twelfth, and so on.

==What Versions of SQL Server are your Components Supported in?==
;Answer:
:Melissa Data currently supports 2008 and 2012 versions of SQL Server. We also provide components for SQL Server 2005 as part of the SSIS Installation, however, it is no longer supported.

[[Category:FAQ]]
[[Category:SSIS:Data Quality Components]]

FAQ:SSIS:Known Issues

2014-03-05T19:14:23Z

Joseph:

FAQ:SSIS:Known Issues

2014-03-05T19:13:39Z

Joseph: Created page with "__FORCETOC__ ==SSIS: Matchup - Date Keys are Not Being Built Correctly== :When using the Component Type: Date in your MatchCode, Date Keys sometimes do not get built in the Ma..."

__FORCETOC__
==SSIS: Matchup - Date Keys are Not Being Built Correctly==
:When using the Component Type: Date in your MatchCode, Date Keys sometimes do not get built in the MatchKey. This is due to a conflict in the expected input format for Dates. Date Inputs should be in the format 'yyyMMdd'. This becomes problematic particularly for some DBMS. SQL Server for example may have a Date Column defined with char[30]. This causes trailing spaces to be included in the Date Input which conflicts with the expected Input Format.

:;Future Resolution
:We will be adding a fix in a later build to trim the trailing white spaces for Date Inputs.

SSIS:Data Quality Components

2014-03-05T18:53:55Z

Joseph:

__NOTOC__
{| border="0" valign="top" style="border-spacing:0px; max-width:1000px;"
|colspan="2"|
{{ProductHeader
|Color=blue
|Image=[[File:MediumTile_SSIS.png|link=]]
|Body=
Melissa Data’s Data Quality Components for SSIS are a suite of custom Data Transformation components for Microsoft's SQL Server SSIS that encapsulate the six levels of complete Data Quality as defined by Gartner™.
}}
|-
|valign="top" colspan="2"|
{{ProductSecond
|Color=orange
|Image=[[File:MediumTile_Current.png|link=]]
|BodyCol1=
<h3>Current Build</h3>
Released February 2013
<br>Build 4.1
*[[Build History:SSIS:Data Quality Components|Build History]]
|BodyCol2=
}}
|-
|valign="top" width="50%" style="padding-right:8px;"|
{{ProductLeft
|Color=green
|Image=[[File:MediumTile_Essentials.png|link=]]
|Body=
<h3>Basics</h3>
*[[Best Practices]]
*[http://www.melissadata.com/webhelp/ssis/updated/index.htm#Getting_Started/Installation.htm Installation Guide]
<h3>Components</h3>
*[http://www.melissadata.com/webhelp/ssis/updated/index.htm#Components/Contact_Verify/Contact_Verify.htm Contact Verify]
*[http://www.melissadata.com/webhelp/ssis/updated/index.htm#Components/Fuzzy_Match/Fuzzy_Match.htm Fuzzy Match]
*[http://www.melissadata.com/webhelp/ssis/updated/index.htm#Components/Global_Verify/Global_Verify.htm Global Verify]
*[http://www.melissadata.com/webhelp/ssis/updated/index.htm#Components/MatchUp/MatchUp.htm MatchUp]
*[http://www.melissadata.com/webhelp/ssis/updated/index.htm#Components/Personator/Personator.htm Personator]
*[http://www.melissadata.com/webhelp/ssis/updated/index.htm#Components/SmartMover/SmartMover.htm SmartMover]
<h3>FAQ</h3>
*[[FAQ:SSIS:Data Quality Components|Data Quality Components for SSIS]]
*[[FAQ:SSIS:Known Issues|Known Issues for SSIS]]
<h3>Tutorials</h3>
*[http://www.melissadata.com/multimedia/ssis-components/general-overview.wmv Overview]
*[http://www.melissadata.com/multimedia/ssis-components/contact-verification-fundamentals.wmv Contact Verify]
*[http://www.melissadata.com/multimedia/ssis-components/fuzzy-matching-fundamentals.wmv Fuzzy Matching]
}}
|valign="top" width="50%" style="padding-left:8px;"|
{{ProductLeft
|Color=red
|Image=[[File:MediumTile_Reference.png|link=]]
|Body=
<h3>Documentation</h3>
*[http://www.melissadata.com/webhelp/ssis/updated/index.htm#SSIS.htm DQC SSIS WebHelp]
*[[Media:DQT_ENT_DQC_QSG.pdf|Data Quality Components for SSIS Quick Start Guide]]
*[http://www.melissadata.com/whitepaper/global-data-integration.asp Global Address Data Integration in SSIS]
<h3>[[Result Codes]]</h3>
*[[Result Codes#AS|Address Status Codes]]
*[[Result Codes#AE|Address Error Codes]]
*[[Result Codes#AC|Address Change Codes]]
*[[Result Codes#Email|Email Result Codes]]
*[[Result Codes#GeoCoder|GeoCoder Result Codes]]
*[[Result Codes#Name|Name Result Codes]]
*[[Result Codes#Phone / Global Phone|Phone Result Codes]]
}}
|}

[[Category:Enterprise Solutions]]
[[Category:SSIS:Data Quality Components]]

SSIS:Data Quality Components

2014-02-05T18:16:27Z

Joseph:

__NOTOC__
{| border="0" valign="top" style="border-spacing:0px; max-width:1000px;"
|colspan="2"|
{{ProductHeader
|Color=blue
|Image=[[File:MediumTile_SSIS.png|link=]]
|Body=
Melissa Data’s Data Quality Components for SSIS are a suite of custom Data Transformation components for Microsoft's SQL Server SSIS that encapsulate the six levels of complete Data Quality as defined by Gartner™.
}}
|-
|valign="top" colspan="2"|
{{ProductSecond
|Color=orange
|Image=[[File:MediumTile_Current.png|link=]]
|BodyCol1=
<h3>Current Build</h3>
Released February 2013
<br>Build 4.1
*[[Build History:SSIS:Data Quality Components|Build History]]
|BodyCol2=
}}
|-
|valign="top" width="50%" style="padding-right:8px;"|
{{ProductLeft
|Color=green
|Image=[[File:MediumTile_Essentials.png|link=]]
|Body=
<h3>Basics</h3>
*[[Best Practices]]
*[http://www.melissadata.com/webhelp/ssis/updated/index.htm#Getting_Started/Installation.htm Installation Guide]
<h3>Components</h3>
*[http://www.melissadata.com/webhelp/ssis/updated/index.htm#Components/Contact_Verify/Contact_Verify.htm Contact Verify]
*[http://www.melissadata.com/webhelp/ssis/updated/index.htm#Components/Fuzzy_Match/Fuzzy_Match.htm Fuzzy Match]
*[http://www.melissadata.com/webhelp/ssis/updated/index.htm#Components/Global_Verify/Global_Verify.htm Global Verify]
*[http://www.melissadata.com/webhelp/ssis/updated/index.htm#Components/MatchUp/MatchUp.htm MatchUp]
*[http://www.melissadata.com/webhelp/ssis/updated/index.htm#Components/Personator/Personator.htm Personator]
*[http://www.melissadata.com/webhelp/ssis/updated/index.htm#Components/SmartMover/SmartMover.htm SmartMover]
<h3>FAQ</h3>
*[[FAQ:SSIS:Data Quality Components|Data Quality Components for SSIS]]
<h3>Tutorials</h3>
*[http://www.melissadata.com/multimedia/ssis-components/general-overview.wmv Overview]
*[http://www.melissadata.com/multimedia/ssis-components/contact-verification-fundamentals.wmv Contact Verify]
*[http://www.melissadata.com/multimedia/ssis-components/fuzzy-matching-fundamentals.wmv Fuzzy Matching]
}}
|valign="top" width="50%" style="padding-left:8px;"|
{{ProductLeft
|Color=red
|Image=[[File:MediumTile_Reference.png|link=]]
|Body=
<h3>Documentation</h3>
*[http://www.melissadata.com/webhelp/ssis/updated/index.htm#SSIS.htm DQC SSIS WebHelp]
*[[Media:DQT_ENT_DQC_QSG.pdf|Data Quality Components for SSIS Quick Start Guide]]
*[http://www.melissadata.com/whitepaper/global-data-integration.asp Global Address Data Integration in SSIS]
<h3>[[Result Codes]]</h3>
*[[Result Codes#AS|Address Status Codes]]
*[[Result Codes#AE|Address Error Codes]]
*[[Result Codes#AC|Address Change Codes]]
*[[Result Codes#Email|Email Result Codes]]
*[[Result Codes#GeoCoder|GeoCoder Result Codes]]
*[[Result Codes#Name|Name Result Codes]]
*[[Result Codes#Phone / Global Phone|Phone Result Codes]]
}}
|}

[[Category:Enterprise Solutions]]
[[Category:SSIS:Data Quality Components]]

Personator Consumer:Build History

2014-02-01T01:51:19Z

Joseph:

{{CustomTOC}}
==Build 3.2.32==
''Released February 2014''

;New Features
*Free Form Input - Personator will now accept single line Input String and parse out the Address, Company, Name, Phone and Email Address. FreeForm Inputs can be both fielded and unfielded.
*Email Append - Personator now has the capability to append Email Addresses

==Build 3.2.14==
''Released July 2013''

;New Features
*Move Update - The Personator Web Service now has the ability to return the current address for an individual or company. This can be done by enabling the action Move.

==Build 1.0.00==
''Released November 2012''

*Initial Release

[[Category:Build History]]
[[Category:Personator]]

Personator Consumer:Build History

2014-02-01T01:50:57Z

Joseph:

{{CustomTOC}}
==Build 3.2.32==
''Released July 2013''

;New Features
*Free Form Input - Personator will now accept single line Input String and parse out the Address, Company, Name, Phone and Email Address. FreeForm Inputs can be both fielded and unfielded.
*Email Append - Personator now has the capability to append Email Addresses

==Build 3.2.14==
''Released July 2013''

;New Features
*Move Update - The Personator Web Service now has the ability to return the current address for an individual or company. This can be done by enabling the action Move.

==Build 1.0.00==
''Released November 2012''

*Initial Release

[[Category:Build History]]
[[Category:Personator]]

Personator Consumer:Build History

2014-02-01T01:50:48Z

Joseph:

Personator Consumer

2014-02-01T01:27:37Z

Joseph:

__NOTOC__
{| border="0" valign="top" style="border-spacing:0px; max-width:1000px;"
|colspan="2"|
{{ProductHeader
|Color=blue
|Image=[[File:MediumTile_Personator.png|link=]]
|Body=
Personator™ Web Service is an all-in-one contact checking, verification, move update, and appending Web service.
}}
|-
|valign="top" colspan="2"|
{{ProductSecond
|Color=orange
|Image=[[File:MediumTile_Current.png|link=]]
|BodyCol1=
<h3>Current Build</h3>
Released January 2014
<br>Build 3.2.23
*[[Build History:Personator|Build History]]
|BodyCol2=

}}
|-
|valign="top" width="50%" style="padding-right:8px;"|
{{ProductLeft
|Color=green
|Image=[[File:MediumTile_Essentials.png|link=]]
|Body=
<h3>Basics</h3>
*[[Best Practices:Web Service|Web Service Best Practices]]
*[[Best Practices:Personator|Personator Best Practices]]
*[[IP Address Information]]
*[[URL:Personator|Service URLs]]
<h3>FAQ</h3>
*[[FAQ:Personator|Personator FAQ]]
<h3>[[Service Samples|Service Sample]]</h3>
*[http://www.melissadata.com/lookups/personator.asp Try the service]
}}
|valign="top" width="50%" style="padding-left:8px;"|
{{ProductLeft
|Color=red
|Image=[[File:MediumTile_Reference.png|link=]]
|Body=
<h3>Documentation</h3>
*[[Media:DQT_WS_Personator_RG.pdf|Personator Reference Guide]]
<h3>[[Result Codes]]</h3>
*[[Result Codes#Personator - Append|Personator Append Codes]]
*[[Result Codes#VR|Personator Verify Record Codes]]
*[[Result Codes#VS|Personator Verify Status Codes]]
*[[Response Result Codes#Personator Response|Personator Web Service Response Error Codes]]
<h3>Sample XML</h3>
*[[Personator:XML Request|XML Request]]
*[[Personator:XML Response|XML Response]]
<h3>Sample Code</h3>
*[ftp://ftp.melissadata.com/SampleCodes/Current/DQWS3/Personator/Per_REST_Java_Win.zip REST Java]
*[ftp://ftp.melissadata.com/SampleCodes/Current/DQWS3/Personator/Per_REST_JavaScript_Win.zip REST JavaScript]
*[ftp://ftp.melissadata.com/SampleCodes/Current/DQWS3/Personator/Per_REST_VB_Win.zip REST VB.Net]
*[ftp://ftp.melissadata.com/SampleCodes/Current/DQWS3/Personator/Per_SOAP_ASP_Win.zip SOAP ASP.Net]
*[ftp://ftp.melissadata.com/SampleCodes/Current/DQWS3/Personator/Per_SOAP_CSharp9_Win.zip SOAP CSharp9]
*[ftp://ftp.melissadata.com/SampleCodes/Current/DQWS3/Personator/Per_SOAP_PHP.zip SOAP PHP]
*[ftp://ftp.melissadata.com/SampleCodes/Current/DQWS3/Personator/Per_XML_CSharp9_Win.zip XML CSharp9]
*[ftp://ftp.melissadata.com/SampleCodes/Current/DQWS3/Personator/Per_XML_Java_Win.zip XML Java]
}}
|}

[[Category:Web Services]]
[[Category:Personator]]

Personator Consumer

2014-02-01T01:27:01Z

Joseph:

__NOTOC__
{| border="0" valign="top" style="border-spacing:0px; max-width:1000px;"
|colspan="2"|
{{ProductHeader
|Color=blue
|Image=[[File:MediumTile_Personator.png|link=]]
|Body=
Personator™ Web Service is an all-in-one contact checking, verification, move update, and appending Web service.
}}
|-
|valign="top" colspan="2"|
{{ProductSecond
|Color=orange
|Image=[[File:MediumTile_Current.png|link=]]
|BodyCol1=
<h3>Current Build</h3>
Released Februrary 2014
<br>Build 3.2.23
*[[Build History:Personator|Build History]]
|BodyCol2=

}}
|-
|valign="top" width="50%" style="padding-right:8px;"|
{{ProductLeft
|Color=green
|Image=[[File:MediumTile_Essentials.png|link=]]
|Body=
<h3>Basics</h3>
*[[Best Practices:Web Service|Web Service Best Practices]]
*[[Best Practices:Personator|Personator Best Practices]]
*[[IP Address Information]]
*[[URL:Personator|Service URLs]]
<h3>FAQ</h3>
*[[FAQ:Personator|Personator FAQ]]
<h3>[[Service Samples|Service Sample]]</h3>
*[http://www.melissadata.com/lookups/personator.asp Try the service]
}}
|valign="top" width="50%" style="padding-left:8px;"|
{{ProductLeft
|Color=red
|Image=[[File:MediumTile_Reference.png|link=]]
|Body=
<h3>Documentation</h3>
*[[Media:DQT_WS_Personator_RG.pdf|Personator Reference Guide]]
<h3>[[Result Codes]]</h3>
*[[Result Codes#Personator - Append|Personator Append Codes]]
*[[Result Codes#VR|Personator Verify Record Codes]]
*[[Result Codes#VS|Personator Verify Status Codes]]
*[[Response Result Codes#Personator Response|Personator Web Service Response Error Codes]]
<h3>Sample XML</h3>
*[[Personator:XML Request|XML Request]]
*[[Personator:XML Response|XML Response]]
<h3>Sample Code</h3>
*[ftp://ftp.melissadata.com/SampleCodes/Current/DQWS3/Personator/Per_REST_Java_Win.zip REST Java]
*[ftp://ftp.melissadata.com/SampleCodes/Current/DQWS3/Personator/Per_REST_JavaScript_Win.zip REST JavaScript]
*[ftp://ftp.melissadata.com/SampleCodes/Current/DQWS3/Personator/Per_REST_VB_Win.zip REST VB.Net]
*[ftp://ftp.melissadata.com/SampleCodes/Current/DQWS3/Personator/Per_SOAP_ASP_Win.zip SOAP ASP.Net]
*[ftp://ftp.melissadata.com/SampleCodes/Current/DQWS3/Personator/Per_SOAP_CSharp9_Win.zip SOAP CSharp9]
*[ftp://ftp.melissadata.com/SampleCodes/Current/DQWS3/Personator/Per_SOAP_PHP.zip SOAP PHP]
*[ftp://ftp.melissadata.com/SampleCodes/Current/DQWS3/Personator/Per_XML_CSharp9_Win.zip XML CSharp9]
*[ftp://ftp.melissadata.com/SampleCodes/Current/DQWS3/Personator/Per_XML_Java_Win.zip XML Java]
}}
|}

[[Category:Web Services]]
[[Category:Personator]]

Personator Consumer

2014-02-01T01:26:51Z

Joseph:

__NOTOC__
{| border="0" valign="top" style="border-spacing:0px; max-width:1000px;"
|colspan="2"|
{{ProductHeader
|Color=blue
|Image=[[File:MediumTile_Personator.png|link=]]
|Body=
Personator™ Web Service is an all-in-one contact checking, verification, move update, and appending Web service.
}}
|-
|valign="top" colspan="2"|
{{ProductSecond
|Color=orange
|Image=[[File:MediumTile_Current.png|link=]]
|BodyCol1=
<h3>Current Build</h3>
Released Februrary 2014
<br>Build 3.2.14
*[[Build History:Personator|Build History]]
|BodyCol2=

}}
|-
|valign="top" width="50%" style="padding-right:8px;"|
{{ProductLeft
|Color=green
|Image=[[File:MediumTile_Essentials.png|link=]]
|Body=
<h3>Basics</h3>
*[[Best Practices:Web Service|Web Service Best Practices]]
*[[Best Practices:Personator|Personator Best Practices]]
*[[IP Address Information]]
*[[URL:Personator|Service URLs]]
<h3>FAQ</h3>
*[[FAQ:Personator|Personator FAQ]]
<h3>[[Service Samples|Service Sample]]</h3>
*[http://www.melissadata.com/lookups/personator.asp Try the service]
}}
|valign="top" width="50%" style="padding-left:8px;"|
{{ProductLeft
|Color=red
|Image=[[File:MediumTile_Reference.png|link=]]
|Body=
<h3>Documentation</h3>
*[[Media:DQT_WS_Personator_RG.pdf|Personator Reference Guide]]
<h3>[[Result Codes]]</h3>
*[[Result Codes#Personator - Append|Personator Append Codes]]
*[[Result Codes#VR|Personator Verify Record Codes]]
*[[Result Codes#VS|Personator Verify Status Codes]]
*[[Response Result Codes#Personator Response|Personator Web Service Response Error Codes]]
<h3>Sample XML</h3>
*[[Personator:XML Request|XML Request]]
*[[Personator:XML Response|XML Response]]
<h3>Sample Code</h3>
*[ftp://ftp.melissadata.com/SampleCodes/Current/DQWS3/Personator/Per_REST_Java_Win.zip REST Java]
*[ftp://ftp.melissadata.com/SampleCodes/Current/DQWS3/Personator/Per_REST_JavaScript_Win.zip REST JavaScript]
*[ftp://ftp.melissadata.com/SampleCodes/Current/DQWS3/Personator/Per_REST_VB_Win.zip REST VB.Net]
*[ftp://ftp.melissadata.com/SampleCodes/Current/DQWS3/Personator/Per_SOAP_ASP_Win.zip SOAP ASP.Net]
*[ftp://ftp.melissadata.com/SampleCodes/Current/DQWS3/Personator/Per_SOAP_CSharp9_Win.zip SOAP CSharp9]
*[ftp://ftp.melissadata.com/SampleCodes/Current/DQWS3/Personator/Per_SOAP_PHP.zip SOAP PHP]
*[ftp://ftp.melissadata.com/SampleCodes/Current/DQWS3/Personator/Per_XML_CSharp9_Win.zip XML CSharp9]
*[ftp://ftp.melissadata.com/SampleCodes/Current/DQWS3/Personator/Per_XML_Java_Win.zip XML Java]
}}
|}

[[Category:Web Services]]
[[Category:Personator]]

Personator Consumer:Build History

2014-02-01T01:22:22Z

Joseph:

{{CustomTOC}}
==Build 3.2.32==
''Released July 2013''

;New Features
*Free Form Input - Personator will now accept single line Input String and parse out the Address, Company, Name, Phone and Email Address.
*Email Append - Personator now has the capability to append Email Addresses

==Build 3.2.14==
''Released July 2013''

;New Features
*Move Update - The Personator Web Service now has the ability to return the current address for an individual or company. This can be done by enabling the action Move.

==Build 1.0.00==
''Released November 2012''

*Initial Release

[[Category:Build History]]
[[Category:Personator]]

Build History:SSIS:Data Quality Components

2014-01-31T23:29:06Z

Joseph:

{{CustomTOC}}
==Build 4.1==
''Released February 2014''
;Contact Verification Component
:Version: 1.0.1.2313
:Address Object Build: 2288
:Name Object Build: 2288
:Phone Object Build: 2288
:Email Object Build: 2288
:Geocoder Object Build: 2312
:MatchUp Object Build: 2137
:Database Date: 01/15/2014

:;Changes
:*Added Congressional District output to MD Cloud mode processing.
:*Updated GUI Display to properly reflect Geocoding level of accuracy when MD Cloud processing.

;Personator Component
:Version: 1.0.0.2313

:;Changes
:*Fixed issues related to difficulties in the inputting of the license string.
:*Fixed Pass-thru All/None button.

;MatchUpComponent
:Version: 2.2.0.2313

:;Changes
:*Added Survivorship processing option.
:*Expression evaluator didn't recognize fields delimited with square brackets.

==Build 3.5==
''Released November 2013''

;Installer Changes
*The following component is now included in the Data Quality Components for SSIS: Personator

;Contact Verification Component
:Version: 1.0.1.2280
:Address Object Build: 2274
:Name Object Build: 2274
:Phone Object Build: 2274
:Email Object Build: 2274
:Geocoder Object Build: 2269
:MatchUp Object Build: 2137
:Database Date: 10/15/2013

:;Changes
:*Fixed rare cloud bug where if an SE01 error did not return 100 records, an incorrect error message was relayed to user.
:*Updated on-premise e-mail options to reflect new build (Fuzzy Lookup and Web Service Lookup options added).
:*Fixed a problem where Input Company did not have a [None] option.
:*Added SSIS variables: CASSFormProcessorName, CASSFormListName, CASSFormName, CASSFormCompany, CASSFormAddress, CASSFormCity,CASSFormState, CASSFormZip, SOAFormProcessorName, SOAFormAddress, SOAFormCity, SOAFormProvince, SOAFormPostalCode, SOAFormFileName
:*Added ability to standardize Company names

;Personator Component
:Version: 1.0.1.2280

:;Changes
:*Added New Personator Component

;SmartMover Component
:Version: 1.0.1.2280

:;Changes
:*Added Community Edition mode, users can demo UI but cannot process.

;Global Verify Component
:Version: 1.0.1.2280

:;Changes
:*Added Community Edition mode, users can demo UI but cannot process.

==Build 08/2013==
''Released August 2013''

;Installer Changes
:The DQC-web.exe Web Installer now installs a set of required data files:
:*mdAddr.dat
:*mdEmail.cfg
:*mdEmail.dat
:*mdName.cfg
:*mdName.dat
:*mdPhone.dat
:*mdPhone.idx
:*ZIPNPA.txt

;Contact Verification Component
:Version: 1.0.1.2233
:Address Object Build: 2214
:Name Object Build: 2214
:Phone Object Build: 2214
:Email Object Build: 2214
:Geocoder Object Build: 2225
:MatchUp Object Build: 2137
:Database Date: 7/15/2013

:;Changes
:*Added the Community Edition for non-licensed users.
:*Added Company Standardization under the Name Tab
:*Added new properties to the output CASS Form

;Smart Mover Component
:Version: 1.0.1.2233
:*Fixed bug (first seen in SmartMover, but likely in all components), where on systems where a full BIDS install was not done, some of the .config settings were not getting loaded.

==Build 05/2013==
''Released May 2013''

;Contact Verification Component
:Version: 1.0.1.2182
:Address Object Build: 2149
:Name Object Build: 2149
:Phone Object Build: 2149
:Email Object Build: 2149
:Geocoder Object Build: 2182
:Database Date: 4/15/201

:;Changes
:*Added MatchUp Community and MatchUp Lite Editions
:*Fixed a bug where you couldn't select "Fixed Length Unicode" on the Default Column Types
:*Fixed bug, in command-line runs Lookup stream sometimes was not getting records populated (you'd just get null fields).
:*Fixed crash when processing with Lookup table and Golden Record.
:*Fixed GUI anomaly, previous changes to Field Mappings would be forgotten if you re-entered that tab from another tab.
:*Addresses that cannot be GeoCoded will now return a Latitude/Longitude of blank instead of zero (0).ed.
:*Old Email Data Files are no longer supported.

:;Deprecated:
:*mdDomain.dat
:*mdEmail.ini
:*mdEmailConfig.ini

:This release includes new data sets for Email and is not backwards compatible.

:;New Data Files
:*mdEmail.dat
:*mdEmail.cfg

:It is required to update both the object and the data files for this update.

==Build 02/2013==
''Released February 2013''

;Contact Verification Component
:Version: 1.0.1.10
:Address Object Build: 2085
:Name Object Build: 2057
:Phone Object Build: 2057
:Email Object Build: 2057
:Geocoder Object Build: 2134
:Database Date: 1/15/2013

;MatchUp Component
:Version 2.1.0.2137
;MatchUp Object Build: 2137

:;Changes
:*Added Golden Record capability to Options tab.
:*Fixed crash when working with very large data sets and limited disk space.
:*User may now specify where work files are stored in 'Advanced Configuration dialog.
:*Improved matching speed in some situations.

==Build 09/2012==
''Released September 2012''

;Intersecting deduper
:Re-Worked Intersecting Deduper for improved performance

;New Match Code Editor Interface
:Simplified and improved the MatchCode Editor

;Added Fuzzy Matching Algorithms
:The following algorithms were added for fuzzy matching compatibility:
:*N-Gram
:*Jaro
:*Jaro-Winkler
:*Longest Common Substring
:*Needleman-Wunsch
:*MD Keyboard
:*Smith-Waterman-Gotoh
:*Dice’s Coefficient
:*Jaccard Similarity
:*Overlap Coefficient
:*Double Metaphone

;Added new Match Code Types
:The following match code types were added to MatchUp:
:*Proximity
:*Numeric
:*Date

;2012 Compatibility
:The Data Quality Components for SSIS is now available and supported in SQL Server 2012

;New Global Component
:Global Component for validating and correcting international addresses is now released for SQL Server 2005, 2008 and 2012.

;Notice
:2005 SSIS Components have been deprecated and are no longer fully supported.

==Build 06/2012==
''Released June 2012''

;Compatibility Summary:
:Address: None. Object and Data file only update.
:Name: None
:Phone: None
:Email: None

;Installer
:If the installer cannot recognize (or mis-recognizes) the version of SQL Server SSIS that you have installed, you can force it to install to a particular version with one of the command-line switches: /Force2005x32, /Force2005x64, /Force2008x32 or /Force2008x64. Only use one of these switches at one time. Often, the installer has recognition issues because a critical component of SQL Server may be missing (such as SSIS services). As a result, after forcing an install in this manner, you may have difficulties using the DQS components.

;Contact Verification Component
:Version: 1.0.1.9
:Address Object Build: 1974
:Name Object Build: 1974
:Phone Object Build: 1974
:Email Object Build: 1974
:Geocoder Object Build: 1979
:Database Date: 5/15/2012

:;Changes
:*Added 'Report result codes for empty input' option to 'Output Filter' tab.
:*User may now specify a proxy server on 'Advanced' dialog.
:*Fixed bug: sometimes the Canadian Geocoding option wasn't getting recognized.

;SmartMover Component
:Version: 1.0.1.6

:;Changes
:*User may now specify a proxy server on 'Advanced' dialog.

;Fuzzy Matching Component
:Version 2.0.0.10

:;Changes
:*Minor name change.

;MatchUp Component
:Version 2.0.0.6
:MatchUp Object Build: 1985

:;Changes
:*Matchcode Editor is now fully integrated into component.
:*Fixed bug, combination result codes not reported in all setup configurations.
:*Fixed crash/hang in certain setup configurations involving passthrough fields.
:*User may now specify where work files are stored in 'Advanced Configuration dialog.
:*New matching data types: Geographic Proximity, Numeric Difference, Date Difference.
:*New fuzzy matching rules: N-Gram, Jaro Distance, Jaro-Winkler Distance, Longest Common Substring, Jaccard Index, Dice's Coefficient, Overlap Coefficient, Needleman-Wunsch, Smith-Waterman-Gotoh, MD Keyboard, Double Metaphone.
:*Improved matching accuracy in some situations.
:*Improved matching speed in some situations.
:*Eliminated certain matchcode requirements and restrictions that were previously required.
:*Added 'Record Suppresion' processing mode.
:*Added 'Record Intersection' processing mode.

[[Category:Build History]]
[[Category:SSIS:Data Quality Components]]

Personator Consumer:FAQ

2014-01-28T19:56:24Z

Joseph:

__FORCETOC__
==What is the Maximum Length Response that we can Expect to Receive for Each Field in Personator?==
;Answer:
:The Web Service Response, in general, does not have a maximum length for each Response Field. This is to avoid any form of truncation when returning information from our data. We do however have recommended values which you can set for defining field lengths in your table.

:{| class="wikitable"
|-
! RESPONSE FIELD !! LENGTH
|-
| MD_NameFull || 256
|-
| MD_CompanyName || 128
|-
| MD_Results || 100
|-
| MD_EmailAddress || 75
|-
| MD_PlaceName || 60
|-
| MD_CBSATitle || 55
|-
| MD_CBSADivisionTitle || 55
|-
| MD_AddressExtras || 50
|-
| MD_AddressLine2 || 50
|-
| MD_AddressLine1 || 50
|-
| MD_DomainName || 50
|-
| MD_AddressStreetName || 40
|-
| MD_NameLast2 || 35
|-
| MD_NameFirst2 || 35
|-
| MD_NameFirst || 35
|-
| MD_City || 35
|-
| MD_CBSALevel || 35
|-
| MD_NameLast || 35
|-
| MD_CBSADivisionLevel || 35
|-
| MD_AddressTypeCode || 31
|-
| MD_PhoneNumber || 30
|-
| MD_StateName || 25
|-
| MD_CountyName || 25
|-
| MD_CountryName || 25
|-
| MD_MailboxName || 25
|-
| MD_NamePrefix || 20
|-
| MD_NameSuffix || 20
|-
| MD_NamePrefix2 || 20
|-
| MD_AddressRouteService || 20
|-
| MD_Suite || 20
|-
| MD_Salutation || 20
|-
| MD_NameMiddle2 || 20
|-
| MD_NameMiddle || 20
|-
| MD_AddressLockBox || 20
|-
| MD_NameSuffix2 || 20
|-
| MD_AddressDeliveryInstallation || 20
|-
| MD_State || 15
|-
| MD_PrivateMailBox || 15
|-
| MD_UrbanizationName || 15
|-
| MD_PhoneExtension || 14
|-
| MD_CityAbbreviation || 13
|-
| MD_Latitude || 12
|-
| MD_Longitude || 12
|-
| MD_DeliveryPointCheckDigit || 11
|-
| MD_AddressKey || 11
|-
| MD_CountryCode || 10
|-
| MD_AddressPrivateMailboxName || 10
|-
| MD_AddressPrivateMailboxRange || 10
|-
| MD_AddressSuiteName || 10
|-
| MD_TopLevelDomain || 10
|-
| MD_PostalCode || 10
|-
| MD_AddressStreetSuffix || 10
|-
| MD_AddressSuiteNumber || 10
|-
| MD_PlaceCode || 7
|-
| MD_UTC || 6
|-
| MD_CensusTract || 6
|-
| MD_AddressPreDirection || 5
|-
| MD_CBSADivisionCode || 5
|-
| MD_CBSACode || 5
|-
| MD_AddressPostDirection || 5
|-
| MD_CountyFIPS || 5
|-
| MD_PhoneSuffix || 4
|-
| MD_AddressHouseNumber || 4
|-
| MD_CensusBlock || 4
|-
| MD_CarrierRoute || 4
|-
| MD_Plus4 || 4
|-
| MD_PhonePrefix || 3
|-
| MD_AreaCode || 3
|-
| MD_NewAreaCode || 3
|-
| MD_DeliveryPointCode || 2
|-
| MD_CongressionalDistrict || 2
|-
| MD_Gender || 1
|-
| MD_DeliveryIndicator || 1
|-
| MD_Gender2 || 1
|}

[[Category:FAQ]]
[[Category:Personator]]

Personator Consumer:FAQ

2014-01-28T18:37:27Z

Joseph:

__FORCETOC__
==How To Set Your License String?==
;Answer:
:[[Set Environment Variable|Set Your Environment Variable For Windows]]

:[[Set Environment Variable#Linux|Set Your Environment Variable For Linux]]

==What development environment will the API work with?==
;Answer:
:This easy to use programmer’s tool is currently provided as a 32 or 64-bit DLL or COM object for Windows and will work with a variety of programming languages. It is also available for Linux, Solaris, AIX, and HPUX.

[[Category:FAQ]]
[[Category:Personator]]

Personator Consumer

2014-01-28T18:35:29Z

Joseph:

__NOTOC__
{| border="0" valign="top" style="border-spacing:0px; max-width:1000px;"
|colspan="2"|
{{ProductHeader
|Color=blue
|Image=[[File:MediumTile_Personator.png|link=]]
|Body=
Personator™ Web Service is an all-in-one contact checking, verification, move update, and appending Web service.
}}
|-
|valign="top" colspan="2"|
{{ProductSecond
|Color=orange
|Image=[[File:MediumTile_Current.png|link=]]
|BodyCol1=
<h3>Current Build</h3>
Released July 2013
<br>Build 3.2.14
*[[Build History:Personator|Build History]]
|BodyCol2=

}}
|-
|valign="top" width="50%" style="padding-right:8px;"|
{{ProductLeft
|Color=green
|Image=[[File:MediumTile_Essentials.png|link=]]
|Body=
<h3>Basics</h3>
*[[Best Practices:Web Service|Web Service Best Practices]]
*[[Best Practices:Personator|Personator Best Practices]]
*[[IP Address Information]]
*[[URL:Personator|Service URLs]]
<h3>FAQ</h3>
*[[FAQ:Personator|Personator FAQ]]
<h3>[[Service Samples|Service Sample]]</h3>
*[http://www.melissadata.com/lookups/personator.asp Try the service]
}}
|valign="top" width="50%" style="padding-left:8px;"|
{{ProductLeft
|Color=red
|Image=[[File:MediumTile_Reference.png|link=]]
|Body=
<h3>Documentation</h3>
*[[Media:DQT_WS_Personator_RG.pdf|Personator Reference Guide]]
<h3>[[Result Codes]]</h3>
*[[Result Codes#Personator - Append|Personator Append Codes]]
*[[Result Codes#VR|Personator Verify Record Codes]]
*[[Result Codes#VS|Personator Verify Status Codes]]
*[[Response Result Codes#Personator Response|Personator Web Service Response Error Codes]]
<h3>Sample XML</h3>
*[[Personator:XML Request|XML Request]]
*[[Personator:XML Response|XML Response]]
<h3>Sample Code</h3>
*[ftp://ftp.melissadata.com/SampleCodes/Current/DQWS3/Personator/Per_REST_Java_Win.zip REST Java]
*[ftp://ftp.melissadata.com/SampleCodes/Current/DQWS3/Personator/Per_REST_JavaScript_Win.zip REST JavaScript]
*[ftp://ftp.melissadata.com/SampleCodes/Current/DQWS3/Personator/Per_REST_VB_Win.zip REST VB.Net]
*[ftp://ftp.melissadata.com/SampleCodes/Current/DQWS3/Personator/Per_SOAP_ASP_Win.zip SOAP ASP.Net]
*[ftp://ftp.melissadata.com/SampleCodes/Current/DQWS3/Personator/Per_SOAP_CSharp9_Win.zip SOAP CSharp9]
*[ftp://ftp.melissadata.com/SampleCodes/Current/DQWS3/Personator/Per_SOAP_PHP.zip SOAP PHP]
*[ftp://ftp.melissadata.com/SampleCodes/Current/DQWS3/Personator/Per_XML_CSharp9_Win.zip XML CSharp9]
*[ftp://ftp.melissadata.com/SampleCodes/Current/DQWS3/Personator/Per_XML_Java_Win.zip XML Java]
}}
|}

[[Category:Web Services]]
[[Category:Personator]]

Personator Consumer:FAQ

2014-01-28T18:34:19Z

Joseph: Joseph moved page FAQ:Web Services to FAQ:Personator

Personator Consumer:FAQ

2014-01-28T18:34:06Z

Joseph: Created page with "__FORCETOC__ ==How To Set Your License String?== ;Answer: :Set Your Environment Variable For Windows :[[Set Environment Variable#Linux|Set Your E..."