Melissa Data Wiki - User contributions [en]

FAQ:SSIS:Data Quality Components

2016-03-22T17:34:44Z

Oscar: /* What Versions of SQL Server/Visual Studio Is Your Components Supported in? */

[[SSIS:Data Quality Components|← SSIS:Data Quality Components]]
{{CustomTOC}}

==What is affected during an install or upgrade?==
;Answer:
:By default the data is stored at this path: C:\Program Files\Melissa DATA\DQT\Data

*Sample Projects is located
** C:\Program Files\Melissa DATA\DQT\DQS\Samples
*Copy of Component DLLS:
**C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2005
**C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2008
**C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2012
**C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2014
*Object DLLS:
**C:\Program Files\Melissa DATA\DQT\DQS\32_bit
**C:\Program Files\Melissa DATA\DQT\DQS\64_bit
*Copy of Config Files:
**C:\Program Files\Melissa DATA\DQT\DQS\Config

Affected During Update or Install:'
*Component Pipeline Dlls:
**C:\Program Files\Microsoft SQL Server\110\DTS\Binn
**C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn
(Note That 110 refers to SQL SERVER 2012, please look for your corresponding version)
*Active Config Used by SSIS:
**C:\ProgramData\Melissa DATA
*Matchup Data Files and Configurations:
**C:\ProgramData\Melissa DATA\MatchUP
(mdMatchup.mc stores your matchcode and will not be overwritten if one exists, you can copy this to a new install to transfer matchcodes.)

==How do I enable On-Premise Global Verify?==
;Answer:
:Please make sure that you have a valid license key that has the local processing enabled. Otherwise the on-premise settings in advanced configuration settings screen will not be visible. You need to set the countries that you want to be processed through locally, the other countries that is not selected will be processed through the Global Verify web service. Please make sure your datafile structures is correct and all datafiles is present, otherwise the dll may crash or reject your settings. When everything is set you can now enter the path for the root folder of your data files into the data path field. You can test to see if you have everything set correctly by pressing test configuration. The tester will report any issues that it finds with your setup. Please contact technical support if you are still having issues with your setup and we will gladly help you out.

==How come I can't process less than 100 records for SmartMover NCOA?==
;Answer:
:USPS regulations state we cannot process NCOA for files less than 100 records. In adherence to the new regulations, SmartMover now checks the first batch to see if it contains less than 100 records. If the batch is less than 100 records we will reject the batch and return an error message. SmartMover will interrupt the processing after processing begins. Please contact your sales representative if you have any questions or concerns regarding this change.

==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]

==How do I make Excel Source Drivers work?==
;Answer:
:The version of the OLE Drivers must match your Office edition (32bit vs 64bit) in your project properties. If you have 32bit Office, click Project then Properties. Under configuration properties, click "debugging" and set "Run64BitRunTime" to False. If you have 64bit Office then set "Run64BitRunTime" to True.

==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/Visual Studio Is Your Components Supported in?==
;Answer:
:Melissa Data currently supports 2008, 2012, and 2014 versions of SQL Server. We also provide components for SQL Server 2005 as part of the SSIS Installation, however, it is no longer supported. Certain Microsoft SQL Server version are supported by specific Microsoft Visual Studio versions for our components. BusinessCoder and future new component will only be offered in SSIS 2010+.

*Microsoft SQL Server 2014 - Microsoft Visual Studio 2013
*Microsoft SQL Server 2012 - Microsoft Visual Studio 2010/2012
*Microsoft SQL Server 2010 - Microsoft Visual Studio 2008
*Microsoft SQL Server 2008 - Microsoft Visual Studio 2005
[[Category:FAQ]]
[[Category:SSIS:Data Quality Components]]

FAQ:SSIS:Component Specific

2016-03-22T17:32:51Z

Oscar:

==Matchup Component FAQ==
Basics:
*[[MatchUp Object:Best Practices|MatchUp Best Practices]]
*[[MatchUp Object:Matchcode Components|Matchcode Components]]
*[[MatchUp Object:Matchcode Mapping|Matchcode Mapping]]
*[[MatchUp Object:Deduping Methods|Deduping Methods]]
*[[MatchUp Object:International Users|International Users]]

Advanced:
*[[MatchUp Object:Matchcode Combinations|Matchcode Combinations]]
*[[MatchUp Object:Blank Field Matching|Blank Field Matching]]
*[[MatchUp Object:Optimizing Matchcodes|Optimizing Matchcodes]]
*[[MatchUp Object:Advanced Algorithms|Information on Advanced Algorithms]]

==Contact Verify Component FAQ==
*[[Address Object:Best Practices|Increasing Address Processing Speeds]]

==Personator Component FAQ==
*[[FAQ:Personator|Personator General FAQ]]

==Profiler Component FAQ==
==Global Verify Component FAQ==
*[[Global Address Verification:FAQ|Global Address Verification General FAQ]]

==SmartMover Component FAQ==
==Fuzzy Match Component FAQ==
==IP Locator Component FAQ==
==Property Component FAQ==
==BusinessCoder Component FAQ==

Build History:SSIS:Data Quality Components

2016-02-17T20:53:29Z

Oscar: /* Build 6.1 */

[[SSIS:Data Quality Components|← SSIS:Data Quality Components]]
{{CustomTOC}}

==Build 6.1==
;''Released February 2016''

;Contact Verification Component
:Version: 1.0.1.2730
:Address Object Build: 2710
:Name Object Build: 2710
:Phone Object Build: 2710
:Email Object Build: 2710
:Geocoder Object Build: 2674
:MatchUp Object Build: 2721
:IpLocator Object Build: 2615
:Database Date: 1/15/2015

:;Changes

:*Email component now has a 'Perform WS Lookup' option for On-Premise processing. With this option enabled, the user can send their emails to the global email webservice for real time validation.
:*Express and Premium modes are now enabled for webservice processing or WS lookup.
:*Various bug fixes.

;Personator Component
:Version: 1.0.0.2730

:;Changes
:*Move Default Set to Strict

;SmartMover Component
:Version: 1.0.1.2730

:;Changes
:*None

;Fuzzy Matching Component
:Version 2.0.0.2730

:;Changes
:*None

;MatchUp Component
:Version 2.2.0.2730

:;Changes
:*Various bug fixes.

;Global Verify Component
:Version 2.0.0.2730
:Global Address Object Build: 2620 (32bit), 2600 (64bit)
:;Changes
:*None

;IP Locator Component
:Version 1.0.0.2730

:;Changes

:*None

;Property Component
:Version 1.0.0.2730

:;Changes

:*None

;Profiler Component
:Version 1.0.0.2730

:;Changes
:*None

==Build 5.4==
;''Released November 2015''
:''Patch Released January 2016 [Build 2683]''

;Contact Verification Component
:Version: 1.0.1.2683
:Address Object Build: 2575
:Name Object Build: 2613
:Phone Object Build: 2613
:Email Object Build: 2554
:Geocoder Object Build: 2670
:MatchUp Object Build: 2628
:IpLocator Object Build: 2615
:Database Date: 10/15/2015

:;Changes

:*Community edition now requires a community edition license key, rather than no license key

;Personator Component
:Version: 1.0.0.2683

:;Changes

:*Fixed an issue with transaction size

;SmartMover Component
:Version: 1.0.1.2683

:;Changes

:*Transaction size setting locked to 100 records in accordance to USPS regulations

;Fuzzy Matching Component
:Version 2.0.0.2683

:;Changes

:*None

;MatchUp Component
:Version 2.2.0.2683

:;Changes

:*International Matchup capabilities now added to Matchup Component
:*Community edition now requires a community edition license key, rather than no license key
:*Fixed an issue where users would experience field mapping issues in a matchcode (address 4-8)
:*Fixed database expiration issue

;Global Verify Component
:Version 2.0.0.2683
:Global Address Object Build: 2620 (32bit), 2600 (64bit)
:;Changes

:*Added new On-Premise component
:*New processing modes: Webservice, On-Premise, Hybrid. WS sends all records to webservice, on-premise sends all records to the local object, and hybrid sends specified records to webservice OR the local object.

;IP Locator Component
:Version 1.0.0.2683

:;Changes

:*None

;Property Component
:Version 1.0.0.2683

:;Changes

:*None

;Profiler Component
:Version 1.0.0.2683

:;Changes

:*Community edition now requires a community edition license key, rather than no license key

==Build 5.3==
''Released August 2015''

;Contact Verification Component
:Version: 1.0.1.2626
:Address Object Build: 2613
:Name Object Build: 2613
:Phone Object Build: 2613
:Email Object Build: 2554
:Geocoder Object Build: 2615
:MatchUp Object Build: 2564
:IpLocator Object Build: 2554
:Database Date: 7/15/2015

:;Changes

:*Added more result codes to the output result filter

;Personator Component
:Version: 1.0.0.2626

:;Changes

:*Fixed a problem where the "Verify" action was not being sent
:*Fixed a problem where the Personator window would crash under certain circumstances
:*Added more result codes to the output result filter

;SmartMover Component
:Version: 1.0.1.2626

:;Changes

:*Files with less than 100 records will not be processed as per USPS regulations

;Fuzzy Matching Component
:Version 2.0.0.2626

:;Changes

:*Fixed spelling error in output tab

;MatchUp Component
:Version 2.2.0.2626

:;Changes

:*Fixed an issue where matchcodes could not use (UK) data types
:*Fixed an issue where DT_Numeric data types could not have a precision value greater than scale value
:*Fixed an issue where the advanced survivorship would crash the component in certain circumstances
:*Fixed several spelling mistakes

;Global Verify Component
:Version 2.0.0.2626
:Global Address Object Build: 2620 (32bit), 2600 (64bit)
:;Changes

:*Added new On-Premise component
:*With a proper license string, users can now verify global data on their machine rather than web service
:*Fixed various issues with On-Premise mode

;IP Locator Component
:Version 1.0.0.2626

:;Changes

:*None

;Property Component
:Version 1.0.0.2626

:;Changes

:*None

;Profiler Component
:Version 1.0.0.2626

:;Changes

:*None

==Build 5.2==
''Released May 2015''

;Contact Verification Component
:Version: 1.0.1.2575
:Address Object Build: 2554
:Name Object Build: 2554
:Phone Object Build: 2554
:Email Object Build: 2554
:Geocoder Object Build: 2554
:MatchUp Object Build: 2554
:IpLocator Object Build: 2554
:Database Date: 4/15/2015

:;Changes

:*fixed "Decimal" option unselectable in "Default Lat/Long Column Type"

;Personator Component
:Version: 1.0.0.2575

:;Changes

:*Personator restriction fixes and GUI changes.
:*Move confidence option now has "Loose" and "Strict" options.

;SmartMover Component
:Version: 1.0.1.2575

:;Changes

:*None

;Fuzzy Matching Component
:Version 2.0.0.2575

:;Changes

:*None

;MatchUp Component
:Version 2.2.0.2575

:;Changes

:*fixed MatchCode Editor swap crash

;Global Verify Component
:Version 2.0.0.2575

:;Changes

:*Fixed a few German translations and spelling
:*German localization for GV.
:*Global Email interface changes.
:*Output filter ES23 description update

;IP Locator Component
:Version 1.0.0.2575

:;Changes

:*None

;Property Component
:Version 1.0.0.2575

:;Changes

:*None

;Profiler Component
:Version 1.0.0.2575

:;Changes

:*Added InferredColumnType column.
:*Fixed issue where users would get error if they didn’t specify any output fields on the passthrough/results pin.

==Build 5.1==
''Released February 2015''

;Contact Verification Component
:Version: 1.0.1.2503
:Address Object Build: 2502
:Name Object Build: 2502
:Phone Object Build: 2502
:Email Object Build: 2502
:Geocoder Object Build: 2502
:MatchUp Object Build: 2408
:IpLocator Object Build: 2502
:Database Date: 1/15/2015

:;Changes

:*Fixed behavior of ‘Output Filter’ tab’s Filter controls in some instances.

;Personator Component
:Version: 1.0.0.2499

:;Changes

:*Added Demographics fields.

;SmartMover Component
:Version: 1.0.1.2503

:;Changes

:*None

;Fuzzy Matching Component
:Version 2.0.0.2502

:;Changes

:*None

;MatchUp Component
:Version 2.2.0.2499

:;Changes

:*Fixed issue where slow machines would crash if user changed tabs quickly during GUI startup.

;Global Verify Component
:Version 2.0.0.2503

:;Changes

:*Dialog not saving changes in rare instances.
:*User is now allowed to pass Advanced Configuration test with only some activated web services.
:*‘Default Lat/Long Column Type’ would not display checkmark if the selection was ‘Decimal’

;IP Locator Component
:Version 1.0.0.2503

:;Changes

:*None

;Property Component
:Version 1.0.0.2499

:;Changes

:*None

;Profiler Component
:Version 1.0.0.2503

:;Changes

:*Fixed issue where users would get error if they didn’t specify any output fields on the passthrough/results pin.

==Build 4.4==
''Released November 2014''
;Contact Verification Component
:Version: 1.0.1.2449
:Address Object Build: 2431
:Name Object Build: 2431
:Phone Object Build: 2431
:Email Object Build: 2431
:Geocoder Object Build: 2441
:MatchUp Object Build: 2441
:IpLocator Object Build: 2441
:Database Date: 10/15/2014

:;Changes

:*None

;Personator Component
:Version: 1.0.0.2449

:;Changes

:*Fixed a problem where output filters were not being saved
:*Improved performance when saving the component

;SmartMover Component
:Version: 1.0.1.2449

:;Changes

:*Fixed a backwards compatibility issue
:*Fixed a problem where output filters were not being saved

;Fuzzy Matching Component
:Version 2.0.0.2449

:;Changes

:*None

;MatchUp Component
:Version 2.2.0.2449

:;Changes

:*None

;Global Verify Component
:Version 2.0.0.2449

:;Changes

:*Added new Name Tab and Functionalities
:*Added new Phone Tab and Functionalities
:*Added new Email Tab and Functionalities

;IP Locator Component
:Version 1.0.0.2449

:;Changes

:*None

;Property Component
:Version 1.0.0.2449

:;Changes

:*New Component

==Build 4.3==
''Released August 2014''
;Contact Verification Component
:Version: 1.0.1. 2419
:Address Object Build: 2381
:Name Object Build: 2381
:Phone Object Build: 2381
:Email Object Build: 2381
:Geocoder Object Build: 2408
:MatchUp Object Build: 2408
:Database Date: 07/15/2014

:;Changes
:*Changed option "Peroform WS Lookup" for Email Check to default to false.
:*Fixed problem with Result Codes when switching from Community Edition to Full Version

;Personator Component
:Version: 1.0.0.2419

:;Changes
:*Fixed a problem where some options were disabled in certain conditions.
:*Pass-through data types now match exactly what is input.

;SmartMover Component
:Version: 1.0.1.2419

:;Changes
:*GUI modifications
:*Component now communicates with new v3 version of SmartMover web service.
:*Added Canadian Change of Address processing via Canadian SmartMover web service.

;Fuzzy Matching Component
:Version 2.0.0.2419

:;Changes
:*Added SSIS data type descriptions to ‘Options’ drop-down menu.

;MatchUp Component
:Version: 2.2.0.2419

:;Changes
:*Added SSIS data type descriptions to ‘Options’ drop-down menu.

;IPLocator Component
:Version: 2.2.0.2419

:;Changes
:*Initial Release

==Build 4.2==
''Released May 2014''

;Compatibility Summary
:The following DLLs are now being compiled in Visual Studio 2012:
:*Address Object
:*Name Object
:*Phone Object
:*Email Object
:*Geocoder Object
:*MatchUp Object

:This requires the installation of the 2012 Visual C++ Redistributable which is included in the SSIS Installation.

;Installer
:The Setup will automatically install 2012 Visual C++ Redistributable (x86 and x64) for compatibility with VS 2012 Compiled DLLs.

;Contact Verification Component
:Version: 1.0.1. 2368
:Address Object Build: 2362
:Name Object Build: 2362
:Phone Object Build: 2362
:Email Object Build: 2362
:Geocoder Object Build: 2362
:MatchUp Object Build: 2362
:Database Date: 04/15/2014

:;Changes

:*Added additional option in the configuration file for DisableAddressSwapping. This option can be set to true in order to permanently disable the swapping of AddressLine1 and AddressLine2.

;Personator Component
:Version: 1.0.0. 2368

:;Changes

:*Added ‘Freeform’ input address field option.
:*Set maximum output field size to 255 instead of 256 (particularly problematic for Excel).
:*Actions were sometimes unselected automatically.
:*Pass-through columns were not always passing through data.
:*Changed verification so that outputting just a result code is not an error.
:*Pass-through's ‘Select All’ button didn’t always work.
:*No default was selected for the Append options.

;MatchUp Component
:Version: 2.2.0. 2368

:;Changes

:*Fixed a problem with date-distance matchcodes; dates with trailing spaces weren’t properly parsed.
:*Fixed a problem with ‘Join with Spaces’ not properly working with an Intersection Lookup source.
:*Fixed a problem where editing survivorship output column size was not getting saved.
:*Survivorship mode ‘Average’ wasn’t working correctly for integers.

;Global Verify Component
:Version: 2.2.0. 2368

:;Changes

:*Added Delivery Lines Option in the GUI for outputting the complete Global Mailing address in AddressLines 1 - 8.

==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]]

FAQ:SSIS:Data Quality Components

2016-02-15T19:21:27Z

Oscar: /* What is affected during an install or upgrade */

[[SSIS:Data Quality Components|← SSIS:Data Quality Components]]
{{CustomTOC}}

==What is affected during an install or upgrade?==
;Answer:
:By default the data is stored at this path: C:\Program Files\Melissa DATA\DQT\Data

*Sample Projects is located
** C:\Program Files\Melissa DATA\DQT\DQS\Samples
*Copy of Component DLLS:
**C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2005
**C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2008
**C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2012
**C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2014
*Object DLLS:
**C:\Program Files\Melissa DATA\DQT\DQS\32_bit
**C:\Program Files\Melissa DATA\DQT\DQS\64_bit
*Copy of Config Files:
**C:\Program Files\Melissa DATA\DQT\DQS\Config

Affected During Update or Install:'
*Component Pipeline Dlls:
**C:\Program Files\Microsoft SQL Server\110\DTS\Binn
**C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn
(Note That 110 refers to SQL SERVER 2012, please look for your corresponding version)
*Active Config Used by SSIS:
**C:\ProgramData\Melissa DATA
*Matchup Data Files and Configurations:
**C:\ProgramData\Melissa DATA\MatchUP
(mdMatchup.mc stores your matchcode and will not be overwritten if one exists, you can copy this to a new install to transfer matchcodes.)

==How do I enable On-Premise Global Verify?==
;Answer:
:Please make sure that you have a valid license key that has the local processing enabled. Otherwise the on-premise settings in advanced configuration settings screen will not be visible. You need to set the countries that you want to be processed through locally, the other countries that is not selected will be processed through the Global Verify web service. Please make sure your datafile structures is correct and all datafiles is present, otherwise the dll may crash or reject your settings. When everything is set you can now enter the path for the root folder of your data files into the data path field. You can test to see if you have everything set correctly by pressing test configuration. The tester will report any issues that it finds with your setup. Please contact technical support if you are still having issues with your setup and we will gladly help you out.

==How come I can't process less than 100 records for SmartMover NCOA?==
;Answer:
:USPS regulations state we cannot process NCOA for files less than 100 records. In adherence to the new regulations, SmartMover now checks the first batch to see if it contains less than 100 records. If the batch is less than 100 records we will reject the batch and return an error message. SmartMover will interrupt the processing after processing begins. Please contact your sales representative if you have any questions or concerns regarding this change.

==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]

==How do I make Excel Source Drivers work?==
;Answer:
:The version of the OLE Drivers must match your Office edition (32bit vs 64bit) in your project properties. If you have 32bit Office, click Project then Properties. Under configuration properties, click "debugging" and set "Run64BitRunTime" to False. If you have 64bit Office then set "Run64BitRunTime" to True.

==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/Visual Studio Is Your Components Supported in?==
;Answer:
:Melissa Data currently supports 2008, 2012, and 2014 versions of SQL Server. We also provide components for SQL Server 2005 as part of the SSIS Installation, however, it is no longer supported. Certain Microsoft SQL Server version are supported by specific Microsoft Visual Studio versions for our components.

*Microsoft SQL Server 2014 - Microsoft Visual Studio 2013
*Microsoft SQL Server 2012 - Microsoft Visual Studio 2010/2012
*Microsoft SQL Server 2010 - Microsoft Visual Studio 2008
*Microsoft SQL Server 2008 - Microsoft Visual Studio 2005
[[Category:FAQ]]
[[Category:SSIS:Data Quality Components]]

Build History:SSIS:Data Quality Components

2016-02-15T19:08:40Z

Oscar: /* Build 6.1 */

[[SSIS:Data Quality Components|← SSIS:Data Quality Components]]
{{CustomTOC}}

==Build 6.1==
;''Released February 2016''

;Contact Verification Component
:Version: 1.0.1.2729
:Address Object Build: 2710
:Name Object Build: 2710
:Phone Object Build: 2710
:Email Object Build: 2710
:Geocoder Object Build: 2674
:MatchUp Object Build: 2721
:IpLocator Object Build: 2615
:Database Date: 1/15/2015

:;Changes

:*Email component now has a 'Perform WS Lookup' option for On-Premise processing. With this option enabled, the user can send their emails to the global email webservice for real time validation.
:*Express and Premium modes are now enabled for webservice processing or WS lookup.
:*Various bug fixes.

;Personator Component
:Version: 1.0.0.2729

:;Changes
:*Move Default Set to Strict

;SmartMover Component
:Version: 1.0.1.2683

:;Changes
:*None

;Fuzzy Matching Component
:Version 2.0.0.2683

:;Changes
:*None

;MatchUp Component
:Version 2.2.0.2683

:;Changes
:*Various bug fixes.

;Global Verify Component
:Version 2.0.0.2683
:Global Address Object Build: 2620 (32bit), 2600 (64bit)
:;Changes
:*None

;IP Locator Component
:Version 1.0.0.2683

:;Changes

:*None

;Property Component
:Version 1.0.0.2683

:;Changes

:*None

;Profiler Component
:Version 1.0.0.2683

:;Changes
:*None

==Build 5.4==
;''Released November 2015''
:''Patch Released January 2016 [Build 2683]''

;Contact Verification Component
:Version: 1.0.1.2683
:Address Object Build: 2575
:Name Object Build: 2613
:Phone Object Build: 2613
:Email Object Build: 2554
:Geocoder Object Build: 2670
:MatchUp Object Build: 2628
:IpLocator Object Build: 2615
:Database Date: 10/15/2015

:;Changes

:*Community edition now requires a community edition license key, rather than no license key

;Personator Component
:Version: 1.0.0.2683

:;Changes

:*Fixed an issue with transaction size

;SmartMover Component
:Version: 1.0.1.2683

:;Changes

:*Transaction size setting locked to 100 records in accordance to USPS regulations

;Fuzzy Matching Component
:Version 2.0.0.2683

:;Changes

:*None

;MatchUp Component
:Version 2.2.0.2683

:;Changes

:*International Matchup capabilities now added to Matchup Component
:*Community edition now requires a community edition license key, rather than no license key
:*Fixed an issue where users would experience field mapping issues in a matchcode (address 4-8)
:*Fixed database expiration issue

;Global Verify Component
:Version 2.0.0.2683
:Global Address Object Build: 2620 (32bit), 2600 (64bit)
:;Changes

:*Added new On-Premise component
:*New processing modes: Webservice, On-Premise, Hybrid. WS sends all records to webservice, on-premise sends all records to the local object, and hybrid sends specified records to webservice OR the local object.

;IP Locator Component
:Version 1.0.0.2683

:;Changes

:*None

;Property Component
:Version 1.0.0.2683

:;Changes

:*None

;Profiler Component
:Version 1.0.0.2683

:;Changes

:*Community edition now requires a community edition license key, rather than no license key

==Build 5.3==
''Released August 2015''

;Contact Verification Component
:Version: 1.0.1.2626
:Address Object Build: 2613
:Name Object Build: 2613
:Phone Object Build: 2613
:Email Object Build: 2554
:Geocoder Object Build: 2615
:MatchUp Object Build: 2564
:IpLocator Object Build: 2554
:Database Date: 7/15/2015

:;Changes

:*Added more result codes to the output result filter

;Personator Component
:Version: 1.0.0.2626

:;Changes

:*Fixed a problem where the "Verify" action was not being sent
:*Fixed a problem where the Personator window would crash under certain circumstances
:*Added more result codes to the output result filter

;SmartMover Component
:Version: 1.0.1.2626

:;Changes

:*Files with less than 100 records will not be processed as per USPS regulations

;Fuzzy Matching Component
:Version 2.0.0.2626

:;Changes

:*Fixed spelling error in output tab

;MatchUp Component
:Version 2.2.0.2626

:;Changes

:*Fixed an issue where matchcodes could not use (UK) data types
:*Fixed an issue where DT_Numeric data types could not have a precision value greater than scale value
:*Fixed an issue where the advanced survivorship would crash the component in certain circumstances
:*Fixed several spelling mistakes

;Global Verify Component
:Version 2.0.0.2626
:Global Address Object Build: 2620 (32bit), 2600 (64bit)
:;Changes

:*Added new On-Premise component
:*With a proper license string, users can now verify global data on their machine rather than web service
:*Fixed various issues with On-Premise mode

;IP Locator Component
:Version 1.0.0.2626

:;Changes

:*None

;Property Component
:Version 1.0.0.2626

:;Changes

:*None

;Profiler Component
:Version 1.0.0.2626

:;Changes

:*None

==Build 5.2==
''Released May 2015''

;Contact Verification Component
:Version: 1.0.1.2575
:Address Object Build: 2554
:Name Object Build: 2554
:Phone Object Build: 2554
:Email Object Build: 2554
:Geocoder Object Build: 2554
:MatchUp Object Build: 2554
:IpLocator Object Build: 2554
:Database Date: 4/15/2015

:;Changes

:*fixed "Decimal" option unselectable in "Default Lat/Long Column Type"

;Personator Component
:Version: 1.0.0.2575

:;Changes

:*Personator restriction fixes and GUI changes.
:*Move confidence option now has "Loose" and "Strict" options.

;SmartMover Component
:Version: 1.0.1.2575

:;Changes

:*None

;Fuzzy Matching Component
:Version 2.0.0.2575

:;Changes

:*None

;MatchUp Component
:Version 2.2.0.2575

:;Changes

:*fixed MatchCode Editor swap crash

;Global Verify Component
:Version 2.0.0.2575

:;Changes

:*Fixed a few German translations and spelling
:*German localization for GV.
:*Global Email interface changes.
:*Output filter ES23 description update

;IP Locator Component
:Version 1.0.0.2575

:;Changes

:*None

;Property Component
:Version 1.0.0.2575

:;Changes

:*None

;Profiler Component
:Version 1.0.0.2575

:;Changes

:*Added InferredColumnType column.
:*Fixed issue where users would get error if they didn’t specify any output fields on the passthrough/results pin.

==Build 5.1==
''Released February 2015''

;Contact Verification Component
:Version: 1.0.1.2503
:Address Object Build: 2502
:Name Object Build: 2502
:Phone Object Build: 2502
:Email Object Build: 2502
:Geocoder Object Build: 2502
:MatchUp Object Build: 2408
:IpLocator Object Build: 2502
:Database Date: 1/15/2015

:;Changes

:*Fixed behavior of ‘Output Filter’ tab’s Filter controls in some instances.

;Personator Component
:Version: 1.0.0.2499

:;Changes

:*Added Demographics fields.

;SmartMover Component
:Version: 1.0.1.2503

:;Changes

:*None

;Fuzzy Matching Component
:Version 2.0.0.2502

:;Changes

:*None

;MatchUp Component
:Version 2.2.0.2499

:;Changes

:*Fixed issue where slow machines would crash if user changed tabs quickly during GUI startup.

;Global Verify Component
:Version 2.0.0.2503

:;Changes

:*Dialog not saving changes in rare instances.
:*User is now allowed to pass Advanced Configuration test with only some activated web services.
:*‘Default Lat/Long Column Type’ would not display checkmark if the selection was ‘Decimal’

;IP Locator Component
:Version 1.0.0.2503

:;Changes

:*None

;Property Component
:Version 1.0.0.2499

:;Changes

:*None

;Profiler Component
:Version 1.0.0.2503

:;Changes

:*Fixed issue where users would get error if they didn’t specify any output fields on the passthrough/results pin.

==Build 4.4==
''Released November 2014''
;Contact Verification Component
:Version: 1.0.1.2449
:Address Object Build: 2431
:Name Object Build: 2431
:Phone Object Build: 2431
:Email Object Build: 2431
:Geocoder Object Build: 2441
:MatchUp Object Build: 2441
:IpLocator Object Build: 2441
:Database Date: 10/15/2014

:;Changes

:*None

;Personator Component
:Version: 1.0.0.2449

:;Changes

:*Fixed a problem where output filters were not being saved
:*Improved performance when saving the component

;SmartMover Component
:Version: 1.0.1.2449

:;Changes

:*Fixed a backwards compatibility issue
:*Fixed a problem where output filters were not being saved

;Fuzzy Matching Component
:Version 2.0.0.2449

:;Changes

:*None

;MatchUp Component
:Version 2.2.0.2449

:;Changes

:*None

;Global Verify Component
:Version 2.0.0.2449

:;Changes

:*Added new Name Tab and Functionalities
:*Added new Phone Tab and Functionalities
:*Added new Email Tab and Functionalities

;IP Locator Component
:Version 1.0.0.2449

:;Changes

:*None

;Property Component
:Version 1.0.0.2449

:;Changes

:*New Component

==Build 4.3==
''Released August 2014''
;Contact Verification Component
:Version: 1.0.1. 2419
:Address Object Build: 2381
:Name Object Build: 2381
:Phone Object Build: 2381
:Email Object Build: 2381
:Geocoder Object Build: 2408
:MatchUp Object Build: 2408
:Database Date: 07/15/2014

:;Changes
:*Changed option "Peroform WS Lookup" for Email Check to default to false.
:*Fixed problem with Result Codes when switching from Community Edition to Full Version

;Personator Component
:Version: 1.0.0.2419

:;Changes
:*Fixed a problem where some options were disabled in certain conditions.
:*Pass-through data types now match exactly what is input.

;SmartMover Component
:Version: 1.0.1.2419

:;Changes
:*GUI modifications
:*Component now communicates with new v3 version of SmartMover web service.
:*Added Canadian Change of Address processing via Canadian SmartMover web service.

;Fuzzy Matching Component
:Version 2.0.0.2419

:;Changes
:*Added SSIS data type descriptions to ‘Options’ drop-down menu.

;MatchUp Component
:Version: 2.2.0.2419

:;Changes
:*Added SSIS data type descriptions to ‘Options’ drop-down menu.

;IPLocator Component
:Version: 2.2.0.2419

:;Changes
:*Initial Release

==Build 4.2==
''Released May 2014''

;Compatibility Summary
:The following DLLs are now being compiled in Visual Studio 2012:
:*Address Object
:*Name Object
:*Phone Object
:*Email Object
:*Geocoder Object
:*MatchUp Object

:This requires the installation of the 2012 Visual C++ Redistributable which is included in the SSIS Installation.

;Installer
:The Setup will automatically install 2012 Visual C++ Redistributable (x86 and x64) for compatibility with VS 2012 Compiled DLLs.

;Contact Verification Component
:Version: 1.0.1. 2368
:Address Object Build: 2362
:Name Object Build: 2362
:Phone Object Build: 2362
:Email Object Build: 2362
:Geocoder Object Build: 2362
:MatchUp Object Build: 2362
:Database Date: 04/15/2014

:;Changes

:*Added additional option in the configuration file for DisableAddressSwapping. This option can be set to true in order to permanently disable the swapping of AddressLine1 and AddressLine2.

;Personator Component
:Version: 1.0.0. 2368

:;Changes

:*Added ‘Freeform’ input address field option.
:*Set maximum output field size to 255 instead of 256 (particularly problematic for Excel).
:*Actions were sometimes unselected automatically.
:*Pass-through columns were not always passing through data.
:*Changed verification so that outputting just a result code is not an error.
:*Pass-through's ‘Select All’ button didn’t always work.
:*No default was selected for the Append options.

;MatchUp Component
:Version: 2.2.0. 2368

:;Changes

:*Fixed a problem with date-distance matchcodes; dates with trailing spaces weren’t properly parsed.
:*Fixed a problem with ‘Join with Spaces’ not properly working with an Intersection Lookup source.
:*Fixed a problem where editing survivorship output column size was not getting saved.
:*Survivorship mode ‘Average’ wasn’t working correctly for integers.

;Global Verify Component
:Version: 2.2.0. 2368

:;Changes

:*Added Delivery Lines Option in the GUI for outputting the complete Global Mailing address in AddressLines 1 - 8.

==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]]

Build History:SSIS:Data Quality Components

2016-02-15T19:08:06Z

Oscar:

[[SSIS:Data Quality Components|← SSIS:Data Quality Components]]
{{CustomTOC}}

==Build 6.1==
;''Released February 2016''

;Contact Verification Component
:Version: 1.0.1.2729
:Address Object Build: 2710
:Name Object Build: 2710
:Phone Object Build: 2710
:Email Object Build: 2710
:Geocoder Object Build: 2674
:MatchUp Object Build: 2721
:IpLocator Object Build: 2615
:Database Date: 1/15/2015

:;Changes

:*Email component now has a 'Perform WS Lookup' option for On-Premise processing. With this option enabled, the user can send their emails to the global email webservice for real time validation.
:*Express and Premium modes are now enabled for webservice processing or WS lookup.
:*Various bug fixes.

;Personator Component
:Version: 1.0.0.2729

:;Changes
:*Move Default Set to Strict

;SmartMover Component
:Version: 1.0.1.2683

:;Changes

;Fuzzy Matching Component
:Version 2.0.0.2683

:;Changes

:*None

;MatchUp Component
:Version 2.2.0.2683

:;Changes

:*Various bug fixes.

;Global Verify Component
:Version 2.0.0.2683
:Global Address Object Build: 2620 (32bit), 2600 (64bit)
:;Changes

;IP Locator Component
:Version 1.0.0.2683

:;Changes

:*None

;Property Component
:Version 1.0.0.2683

:;Changes

:*None

;Profiler Component
:Version 1.0.0.2683

:;Changes

==Build 5.4==
;''Released November 2015''
:''Patch Released January 2016 [Build 2683]''

;Contact Verification Component
:Version: 1.0.1.2683
:Address Object Build: 2575
:Name Object Build: 2613
:Phone Object Build: 2613
:Email Object Build: 2554
:Geocoder Object Build: 2670
:MatchUp Object Build: 2628
:IpLocator Object Build: 2615
:Database Date: 10/15/2015

:;Changes

:*Community edition now requires a community edition license key, rather than no license key

;Personator Component
:Version: 1.0.0.2683

:;Changes

:*Fixed an issue with transaction size

;SmartMover Component
:Version: 1.0.1.2683

:;Changes

:*Transaction size setting locked to 100 records in accordance to USPS regulations

;Fuzzy Matching Component
:Version 2.0.0.2683

:;Changes

:*None

;MatchUp Component
:Version 2.2.0.2683

:;Changes

:*International Matchup capabilities now added to Matchup Component
:*Community edition now requires a community edition license key, rather than no license key
:*Fixed an issue where users would experience field mapping issues in a matchcode (address 4-8)
:*Fixed database expiration issue

;Global Verify Component
:Version 2.0.0.2683
:Global Address Object Build: 2620 (32bit), 2600 (64bit)
:;Changes

:*Added new On-Premise component
:*New processing modes: Webservice, On-Premise, Hybrid. WS sends all records to webservice, on-premise sends all records to the local object, and hybrid sends specified records to webservice OR the local object.

;IP Locator Component
:Version 1.0.0.2683

:;Changes

:*None

;Property Component
:Version 1.0.0.2683

:;Changes

:*None

;Profiler Component
:Version 1.0.0.2683

:;Changes

:*Community edition now requires a community edition license key, rather than no license key

==Build 5.3==
''Released August 2015''

;Contact Verification Component
:Version: 1.0.1.2626
:Address Object Build: 2613
:Name Object Build: 2613
:Phone Object Build: 2613
:Email Object Build: 2554
:Geocoder Object Build: 2615
:MatchUp Object Build: 2564
:IpLocator Object Build: 2554
:Database Date: 7/15/2015

:;Changes

:*Added more result codes to the output result filter

;Personator Component
:Version: 1.0.0.2626

:;Changes

:*Fixed a problem where the "Verify" action was not being sent
:*Fixed a problem where the Personator window would crash under certain circumstances
:*Added more result codes to the output result filter

;SmartMover Component
:Version: 1.0.1.2626

:;Changes

:*Files with less than 100 records will not be processed as per USPS regulations

;Fuzzy Matching Component
:Version 2.0.0.2626

:;Changes

:*Fixed spelling error in output tab

;MatchUp Component
:Version 2.2.0.2626

:;Changes

:*Fixed an issue where matchcodes could not use (UK) data types
:*Fixed an issue where DT_Numeric data types could not have a precision value greater than scale value
:*Fixed an issue where the advanced survivorship would crash the component in certain circumstances
:*Fixed several spelling mistakes

;Global Verify Component
:Version 2.0.0.2626
:Global Address Object Build: 2620 (32bit), 2600 (64bit)
:;Changes

:*Added new On-Premise component
:*With a proper license string, users can now verify global data on their machine rather than web service
:*Fixed various issues with On-Premise mode

;IP Locator Component
:Version 1.0.0.2626

:;Changes

:*None

;Property Component
:Version 1.0.0.2626

:;Changes

:*None

;Profiler Component
:Version 1.0.0.2626

:;Changes

:*None

==Build 5.2==
''Released May 2015''

;Contact Verification Component
:Version: 1.0.1.2575
:Address Object Build: 2554
:Name Object Build: 2554
:Phone Object Build: 2554
:Email Object Build: 2554
:Geocoder Object Build: 2554
:MatchUp Object Build: 2554
:IpLocator Object Build: 2554
:Database Date: 4/15/2015

:;Changes

:*fixed "Decimal" option unselectable in "Default Lat/Long Column Type"

;Personator Component
:Version: 1.0.0.2575

:;Changes

:*Personator restriction fixes and GUI changes.
:*Move confidence option now has "Loose" and "Strict" options.

;SmartMover Component
:Version: 1.0.1.2575

:;Changes

:*None

;Fuzzy Matching Component
:Version 2.0.0.2575

:;Changes

:*None

;MatchUp Component
:Version 2.2.0.2575

:;Changes

:*fixed MatchCode Editor swap crash

;Global Verify Component
:Version 2.0.0.2575

:;Changes

:*Fixed a few German translations and spelling
:*German localization for GV.
:*Global Email interface changes.
:*Output filter ES23 description update

;IP Locator Component
:Version 1.0.0.2575

:;Changes

:*None

;Property Component
:Version 1.0.0.2575

:;Changes

:*None

;Profiler Component
:Version 1.0.0.2575

:;Changes

:*Added InferredColumnType column.
:*Fixed issue where users would get error if they didn’t specify any output fields on the passthrough/results pin.

==Build 5.1==
''Released February 2015''

;Contact Verification Component
:Version: 1.0.1.2503
:Address Object Build: 2502
:Name Object Build: 2502
:Phone Object Build: 2502
:Email Object Build: 2502
:Geocoder Object Build: 2502
:MatchUp Object Build: 2408
:IpLocator Object Build: 2502
:Database Date: 1/15/2015

:;Changes

:*Fixed behavior of ‘Output Filter’ tab’s Filter controls in some instances.

;Personator Component
:Version: 1.0.0.2499

:;Changes

:*Added Demographics fields.

;SmartMover Component
:Version: 1.0.1.2503

:;Changes

:*None

;Fuzzy Matching Component
:Version 2.0.0.2502

:;Changes

:*None

;MatchUp Component
:Version 2.2.0.2499

:;Changes

:*Fixed issue where slow machines would crash if user changed tabs quickly during GUI startup.

;Global Verify Component
:Version 2.0.0.2503

:;Changes

:*Dialog not saving changes in rare instances.
:*User is now allowed to pass Advanced Configuration test with only some activated web services.
:*‘Default Lat/Long Column Type’ would not display checkmark if the selection was ‘Decimal’

;IP Locator Component
:Version 1.0.0.2503

:;Changes

:*None

;Property Component
:Version 1.0.0.2499

:;Changes

:*None

;Profiler Component
:Version 1.0.0.2503

:;Changes

:*Fixed issue where users would get error if they didn’t specify any output fields on the passthrough/results pin.

==Build 4.4==
''Released November 2014''
;Contact Verification Component
:Version: 1.0.1.2449
:Address Object Build: 2431
:Name Object Build: 2431
:Phone Object Build: 2431
:Email Object Build: 2431
:Geocoder Object Build: 2441
:MatchUp Object Build: 2441
:IpLocator Object Build: 2441
:Database Date: 10/15/2014

:;Changes

:*None

;Personator Component
:Version: 1.0.0.2449

:;Changes

:*Fixed a problem where output filters were not being saved
:*Improved performance when saving the component

;SmartMover Component
:Version: 1.0.1.2449

:;Changes

:*Fixed a backwards compatibility issue
:*Fixed a problem where output filters were not being saved

;Fuzzy Matching Component
:Version 2.0.0.2449

:;Changes

:*None

;MatchUp Component
:Version 2.2.0.2449

:;Changes

:*None

;Global Verify Component
:Version 2.0.0.2449

:;Changes

:*Added new Name Tab and Functionalities
:*Added new Phone Tab and Functionalities
:*Added new Email Tab and Functionalities

;IP Locator Component
:Version 1.0.0.2449

:;Changes

:*None

;Property Component
:Version 1.0.0.2449

:;Changes

:*New Component

==Build 4.3==
''Released August 2014''
;Contact Verification Component
:Version: 1.0.1. 2419
:Address Object Build: 2381
:Name Object Build: 2381
:Phone Object Build: 2381
:Email Object Build: 2381
:Geocoder Object Build: 2408
:MatchUp Object Build: 2408
:Database Date: 07/15/2014

:;Changes
:*Changed option "Peroform WS Lookup" for Email Check to default to false.
:*Fixed problem with Result Codes when switching from Community Edition to Full Version

;Personator Component
:Version: 1.0.0.2419

:;Changes
:*Fixed a problem where some options were disabled in certain conditions.
:*Pass-through data types now match exactly what is input.

;SmartMover Component
:Version: 1.0.1.2419

:;Changes
:*GUI modifications
:*Component now communicates with new v3 version of SmartMover web service.
:*Added Canadian Change of Address processing via Canadian SmartMover web service.

;Fuzzy Matching Component
:Version 2.0.0.2419

:;Changes
:*Added SSIS data type descriptions to ‘Options’ drop-down menu.

;MatchUp Component
:Version: 2.2.0.2419

:;Changes
:*Added SSIS data type descriptions to ‘Options’ drop-down menu.

;IPLocator Component
:Version: 2.2.0.2419

:;Changes
:*Initial Release

==Build 4.2==
''Released May 2014''

;Compatibility Summary
:The following DLLs are now being compiled in Visual Studio 2012:
:*Address Object
:*Name Object
:*Phone Object
:*Email Object
:*Geocoder Object
:*MatchUp Object

:This requires the installation of the 2012 Visual C++ Redistributable which is included in the SSIS Installation.

;Installer
:The Setup will automatically install 2012 Visual C++ Redistributable (x86 and x64) for compatibility with VS 2012 Compiled DLLs.

;Contact Verification Component
:Version: 1.0.1. 2368
:Address Object Build: 2362
:Name Object Build: 2362
:Phone Object Build: 2362
:Email Object Build: 2362
:Geocoder Object Build: 2362
:MatchUp Object Build: 2362
:Database Date: 04/15/2014

:;Changes

:*Added additional option in the configuration file for DisableAddressSwapping. This option can be set to true in order to permanently disable the swapping of AddressLine1 and AddressLine2.

;Personator Component
:Version: 1.0.0. 2368

:;Changes

:*Added ‘Freeform’ input address field option.
:*Set maximum output field size to 255 instead of 256 (particularly problematic for Excel).
:*Actions were sometimes unselected automatically.
:*Pass-through columns were not always passing through data.
:*Changed verification so that outputting just a result code is not an error.
:*Pass-through's ‘Select All’ button didn’t always work.
:*No default was selected for the Append options.

;MatchUp Component
:Version: 2.2.0. 2368

:;Changes

:*Fixed a problem with date-distance matchcodes; dates with trailing spaces weren’t properly parsed.
:*Fixed a problem with ‘Join with Spaces’ not properly working with an Intersection Lookup source.
:*Fixed a problem where editing survivorship output column size was not getting saved.
:*Survivorship mode ‘Average’ wasn’t working correctly for integers.

;Global Verify Component
:Version: 2.2.0. 2368

:;Changes

:*Added Delivery Lines Option in the GUI for outputting the complete Global Mailing address in AddressLines 1 - 8.

==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]]

SSIS:Data Quality Components

2016-02-15T17:41:54Z

Oscar:

__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 2016
<br>Build 6.1
*[[Build History:SSIS:Data Quality Components|Build History]]
|BodyCol2=
<h3>Notices</h3>
*[[FAQ:SSIS:Known Issues|Known Issues]]
}}
|-
|valign="top" width="50%" style="padding-right:8px;"|
{{ProductLeft
|Color=green
|Image=[[File:MediumTile_Essentials.png|link=]]
|Body=
<h3>Basics</h3>
*[[SSIS:Best Practices|SSIS Best Practices]]
*[[SSIS:Installation|Installation]]
<h3>FAQ</h3>
*[[FAQ:SSIS:Data Quality Components|Data Quality Components for SSIS]]
*[[FAQ:SSIS:Data Type Conversions|Data Type Conversions]]
*[[FAQ:SSIS:Component Specific|Component Specific FAQ & Optimizations]]
<h3>Tutorial Videos</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>
*[[SSIS:Reference|DQC SSIS Online Reference]]
*[[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 Code Details#SSIS Data Quality Components|SSIS DQC Result Codes]]
}}
|}

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

FAQ:SSIS:Data Quality Components

2016-02-04T00:08:32Z

Oscar: /* What is affected during an install or upgrade */

[[SSIS:Data Quality Components|← SSIS:Data Quality Components]]
{{CustomTOC}}

==What is affected during an install or upgrade==
;Answer:
:By default the data is stored at this path: C:\Program Files\Melissa DATA\DQT\Data

*Sample Projects is located
** C:\Program Files\Melissa DATA\DQT\DQS\Samples
*Copy of Component DLLS:
**C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2005
**C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2008
**C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2012
**C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2014
*Object DLLS:
**C:\Program Files\Melissa DATA\DQT\DQS\32_bit
**C:\Program Files\Melissa DATA\DQT\DQS\64_bit
*Copy of Config Files:
**C:\Program Files\Melissa DATA\DQT\DQS\Config

Affected During Update or Install:'
*Component Pipeline Dlls:
**C:\Program Files\Microsoft SQL Server\110\DTS\Binn
**C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn
(Note That 110 refers to SQL SERVER 2012, please look for your corresponding version)
*Active Config Used by SSIS:
**C:\ProgramData\Melissa DATA
*Matchup Data Files and Configurations:
**C:\ProgramData\Melissa DATA\MatchUP
(mdMatchup.mc stores your matchcode and will not be overwritten if one exists, you can copy this to a new install to transfer matchcodes.)

==How do I enable On-Premise Global Verify?==
;Answer:
:Please make sure that you have a valid license key that has the local processing enabled. Otherwise the on-premise settings in advanced configuration settings screen will not be visible. You need to set the countries that you want to be processed through locally, the other countries that is not selected will be processed through the Global Verify web service. Please make sure your datafile structures is correct and all datafiles is present, otherwise the dll may crash or reject your settings. When everything is set you can now enter the path for the root folder of your data files into the data path field. You can test to see if you have everything set correctly by pressing test configuration. The tester will report any issues that it finds with your setup. Please contact technical support if you are still having issues with your setup and we will gladly help you out.

==How come I can't process less than 100 records for SmartMover NCOA?==
;Answer:
:USPS regulations state we cannot process NCOA for files less than 100 records. In adherence to the new regulations, SmartMover now checks the first batch to see if it contains less than 100 records. If the batch is less than 100 records we will reject the batch and return an error message. SmartMover will interrupt the processing after processing begins. Please contact your sales representative if you have any questions or concerns regarding this change.

==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]

==How do I make Excel Source Drivers work?==
;Answer:
:The version of the OLE Drivers must match your Office edition (32bit vs 64bit) in your project properties. If you have 32bit Office, click Project then Properties. Under configuration properties, click "debugging" and set "Run64BitRunTime" to False. If you have 64bit Office then set "Run64BitRunTime" to True.

==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/Visual Studio Is Your Components Supported in?==
;Answer:
:Melissa Data currently supports 2008, 2012, and 2014 versions of SQL Server. We also provide components for SQL Server 2005 as part of the SSIS Installation, however, it is no longer supported. Certain Microsoft SQL Server version are supported by specific Microsoft Visual Studio versions for our components.

*Microsoft SQL Server 2014 - Microsoft Visual Studio 2013
*Microsoft SQL Server 2012 - Microsoft Visual Studio 2010/2012
*Microsoft SQL Server 2010 - Microsoft Visual Studio 2008
*Microsoft SQL Server 2008 - Microsoft Visual Studio 2005
[[Category:FAQ]]
[[Category:SSIS:Data Quality Components]]

FAQ:SSIS:Data Quality Components

2016-02-04T00:07:30Z

Oscar: /* What is affected during an install or upgrade */

[[SSIS:Data Quality Components|← SSIS:Data Quality Components]]
{{CustomTOC}}

==What is affected during an install or upgrade==
;Answer:
:By default the data is stored at this path: C:\Program Files\Melissa DATA\DQT\Data

*Sample Projects is located
** C:\Program Files\Melissa DATA\DQT\DQS\Samples
*Copy of Component DLLS:
**C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2005
**C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2008
**C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2012
**C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2014
*Object DLLS:
**C:\Program Files\Melissa DATA\DQT\DQS\32_bit
**C:\Program Files\Melissa DATA\DQT\DQS\64_bit
*Copy of Config Files:
**C:\Program Files\Melissa DATA\DQT\DQS\Config

Affected During Update or Install:'
*Component Pipeline Dlls:
**C:\Program Files\Microsoft SQL Server\110\DTS\Binn
**C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn
(Note That 110 refers to SQL SERVER 2012, please look for your corresponding version)
*Active Config Used by SSIS:
**C:\ProgramData\Melissa DATA

==How do I enable On-Premise Global Verify?==
;Answer:
:Please make sure that you have a valid license key that has the local processing enabled. Otherwise the on-premise settings in advanced configuration settings screen will not be visible. You need to set the countries that you want to be processed through locally, the other countries that is not selected will be processed through the Global Verify web service. Please make sure your datafile structures is correct and all datafiles is present, otherwise the dll may crash or reject your settings. When everything is set you can now enter the path for the root folder of your data files into the data path field. You can test to see if you have everything set correctly by pressing test configuration. The tester will report any issues that it finds with your setup. Please contact technical support if you are still having issues with your setup and we will gladly help you out.

==How come I can't process less than 100 records for SmartMover NCOA?==
;Answer:
:USPS regulations state we cannot process NCOA for files less than 100 records. In adherence to the new regulations, SmartMover now checks the first batch to see if it contains less than 100 records. If the batch is less than 100 records we will reject the batch and return an error message. SmartMover will interrupt the processing after processing begins. Please contact your sales representative if you have any questions or concerns regarding this change.

==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]

==How do I make Excel Source Drivers work?==
;Answer:
:The version of the OLE Drivers must match your Office edition (32bit vs 64bit) in your project properties. If you have 32bit Office, click Project then Properties. Under configuration properties, click "debugging" and set "Run64BitRunTime" to False. If you have 64bit Office then set "Run64BitRunTime" to True.

==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/Visual Studio Is Your Components Supported in?==
;Answer:
:Melissa Data currently supports 2008, 2012, and 2014 versions of SQL Server. We also provide components for SQL Server 2005 as part of the SSIS Installation, however, it is no longer supported. Certain Microsoft SQL Server version are supported by specific Microsoft Visual Studio versions for our components.

*Microsoft SQL Server 2014 - Microsoft Visual Studio 2013
*Microsoft SQL Server 2012 - Microsoft Visual Studio 2010/2012
*Microsoft SQL Server 2010 - Microsoft Visual Studio 2008
*Microsoft SQL Server 2008 - Microsoft Visual Studio 2005
[[Category:FAQ]]
[[Category:SSIS:Data Quality Components]]

FAQ:SSIS:Data Quality Components

2016-02-04T00:06:54Z

Oscar: /* What is affected during an install or upgrade */

[[SSIS:Data Quality Components|← SSIS:Data Quality Components]]
{{CustomTOC}}

==What is affected during an install or upgrade==
;Answer:
:By default the data is stored at this path: C:\Program Files\Melissa DATA\DQT\Data

*Sample Projects is located
** C:\Program Files\Melissa DATA\DQT\DQS\Samples
*Copy of Component DLLS:
**C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2005
**C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2008
**C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2012
**C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2014
*Object DLLS:
**C:\Program Files\Melissa DATA\DQT\DQS\32_bit
**C:\Program Files\Melissa DATA\DQT\DQS\64_bit
*Copy of Config Files:
**C:\Program Files\Melissa DATA\DQT\DQS\Config

Affected During Update or Install:'
*Component Pipeline Dlls:
C:\Program Files\Microsoft SQL Server\110\DTS\Binn
C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn
(Note That 110 refers to SQL SERVER 2012, please look for your corresponding version)

==How do I enable On-Premise Global Verify?==
;Answer:
:Please make sure that you have a valid license key that has the local processing enabled. Otherwise the on-premise settings in advanced configuration settings screen will not be visible. You need to set the countries that you want to be processed through locally, the other countries that is not selected will be processed through the Global Verify web service. Please make sure your datafile structures is correct and all datafiles is present, otherwise the dll may crash or reject your settings. When everything is set you can now enter the path for the root folder of your data files into the data path field. You can test to see if you have everything set correctly by pressing test configuration. The tester will report any issues that it finds with your setup. Please contact technical support if you are still having issues with your setup and we will gladly help you out.

==How come I can't process less than 100 records for SmartMover NCOA?==
;Answer:
:USPS regulations state we cannot process NCOA for files less than 100 records. In adherence to the new regulations, SmartMover now checks the first batch to see if it contains less than 100 records. If the batch is less than 100 records we will reject the batch and return an error message. SmartMover will interrupt the processing after processing begins. Please contact your sales representative if you have any questions or concerns regarding this change.

==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]

==How do I make Excel Source Drivers work?==
;Answer:
:The version of the OLE Drivers must match your Office edition (32bit vs 64bit) in your project properties. If you have 32bit Office, click Project then Properties. Under configuration properties, click "debugging" and set "Run64BitRunTime" to False. If you have 64bit Office then set "Run64BitRunTime" to True.

==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/Visual Studio Is Your Components Supported in?==
;Answer:
:Melissa Data currently supports 2008, 2012, and 2014 versions of SQL Server. We also provide components for SQL Server 2005 as part of the SSIS Installation, however, it is no longer supported. Certain Microsoft SQL Server version are supported by specific Microsoft Visual Studio versions for our components.

*Microsoft SQL Server 2014 - Microsoft Visual Studio 2013
*Microsoft SQL Server 2012 - Microsoft Visual Studio 2010/2012
*Microsoft SQL Server 2010 - Microsoft Visual Studio 2008
*Microsoft SQL Server 2008 - Microsoft Visual Studio 2005
[[Category:FAQ]]
[[Category:SSIS:Data Quality Components]]

FAQ:SSIS:Data Quality Components

2016-02-04T00:05:35Z

Oscar: /* What is affected during an install or upgrade */

[[SSIS:Data Quality Components|← SSIS:Data Quality Components]]
{{CustomTOC}}

==What is affected during an install or upgrade==
;Answer:
:By default the data is stored at this path: C:\Program Files\Melissa DATA\DQT\Data

*Sample Projects is located
** C:\Program Files\Melissa DATA\DQT\DQS\Samples
*Copy of Component DLLS:
**C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2005
**C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2008
**C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2012
**C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2014
*Object DLLS:
**C:\Program Files\Melissa DATA\DQT\DQS\32_bit
**C:\Program Files\Melissa DATA\DQT\DQS\64_bit
*Copy of Config Files:
**C:\Program Files\Melissa DATA\DQT\DQS\Config

==How do I enable On-Premise Global Verify?==
;Answer:
:Please make sure that you have a valid license key that has the local processing enabled. Otherwise the on-premise settings in advanced configuration settings screen will not be visible. You need to set the countries that you want to be processed through locally, the other countries that is not selected will be processed through the Global Verify web service. Please make sure your datafile structures is correct and all datafiles is present, otherwise the dll may crash or reject your settings. When everything is set you can now enter the path for the root folder of your data files into the data path field. You can test to see if you have everything set correctly by pressing test configuration. The tester will report any issues that it finds with your setup. Please contact technical support if you are still having issues with your setup and we will gladly help you out.

==How come I can't process less than 100 records for SmartMover NCOA?==
;Answer:
:USPS regulations state we cannot process NCOA for files less than 100 records. In adherence to the new regulations, SmartMover now checks the first batch to see if it contains less than 100 records. If the batch is less than 100 records we will reject the batch and return an error message. SmartMover will interrupt the processing after processing begins. Please contact your sales representative if you have any questions or concerns regarding this change.

==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]

==How do I make Excel Source Drivers work?==
;Answer:
:The version of the OLE Drivers must match your Office edition (32bit vs 64bit) in your project properties. If you have 32bit Office, click Project then Properties. Under configuration properties, click "debugging" and set "Run64BitRunTime" to False. If you have 64bit Office then set "Run64BitRunTime" to True.

==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/Visual Studio Is Your Components Supported in?==
;Answer:
:Melissa Data currently supports 2008, 2012, and 2014 versions of SQL Server. We also provide components for SQL Server 2005 as part of the SSIS Installation, however, it is no longer supported. Certain Microsoft SQL Server version are supported by specific Microsoft Visual Studio versions for our components.

*Microsoft SQL Server 2014 - Microsoft Visual Studio 2013
*Microsoft SQL Server 2012 - Microsoft Visual Studio 2010/2012
*Microsoft SQL Server 2010 - Microsoft Visual Studio 2008
*Microsoft SQL Server 2008 - Microsoft Visual Studio 2005
[[Category:FAQ]]
[[Category:SSIS:Data Quality Components]]

FAQ:SSIS:Data Quality Components

2016-02-04T00:05:23Z

Oscar: /* What is affected during an install or upgrade */

[[SSIS:Data Quality Components|← SSIS:Data Quality Components]]
{{CustomTOC}}

==What is affected during an install or upgrade==
;Answer:
:By default the data is stored at this path: C:\Program Files\Melissa DATA\DQT\Data

*Sample Projects is located
** C:\Program Files\Melissa DATA\DQT\DQS\Samples
*Component DLLS:
**C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2005
**C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2008
**C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2012
**C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2014
*Object DLLS:
**C:\Program Files\Melissa DATA\DQT\DQS\32_bit
**C:\Program Files\Melissa DATA\DQT\DQS\64_bit
*Copy of Config Files:
**C:\Program Files\Melissa DATA\DQT\DQS\Config

==How do I enable On-Premise Global Verify?==
;Answer:
:Please make sure that you have a valid license key that has the local processing enabled. Otherwise the on-premise settings in advanced configuration settings screen will not be visible. You need to set the countries that you want to be processed through locally, the other countries that is not selected will be processed through the Global Verify web service. Please make sure your datafile structures is correct and all datafiles is present, otherwise the dll may crash or reject your settings. When everything is set you can now enter the path for the root folder of your data files into the data path field. You can test to see if you have everything set correctly by pressing test configuration. The tester will report any issues that it finds with your setup. Please contact technical support if you are still having issues with your setup and we will gladly help you out.

==How come I can't process less than 100 records for SmartMover NCOA?==
;Answer:
:USPS regulations state we cannot process NCOA for files less than 100 records. In adherence to the new regulations, SmartMover now checks the first batch to see if it contains less than 100 records. If the batch is less than 100 records we will reject the batch and return an error message. SmartMover will interrupt the processing after processing begins. Please contact your sales representative if you have any questions or concerns regarding this change.

==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]

==How do I make Excel Source Drivers work?==
;Answer:
:The version of the OLE Drivers must match your Office edition (32bit vs 64bit) in your project properties. If you have 32bit Office, click Project then Properties. Under configuration properties, click "debugging" and set "Run64BitRunTime" to False. If you have 64bit Office then set "Run64BitRunTime" to True.

==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/Visual Studio Is Your Components Supported in?==
;Answer:
:Melissa Data currently supports 2008, 2012, and 2014 versions of SQL Server. We also provide components for SQL Server 2005 as part of the SSIS Installation, however, it is no longer supported. Certain Microsoft SQL Server version are supported by specific Microsoft Visual Studio versions for our components.

*Microsoft SQL Server 2014 - Microsoft Visual Studio 2013
*Microsoft SQL Server 2012 - Microsoft Visual Studio 2010/2012
*Microsoft SQL Server 2010 - Microsoft Visual Studio 2008
*Microsoft SQL Server 2008 - Microsoft Visual Studio 2005
[[Category:FAQ]]
[[Category:SSIS:Data Quality Components]]

FAQ:SSIS:Data Quality Components

2016-02-04T00:05:00Z

Oscar: /* What is affected during an install or upgrade */

[[SSIS:Data Quality Components|← SSIS:Data Quality Components]]
{{CustomTOC}}

==What is affected during an install or upgrade==
;Answer:
:By default the data is stored at this path: C:\Program Files\Melissa DATA\DQT\Data

*Sample Projects is located
** C:\Program Files\Melissa DATA\DQT\DQS\Samples
*Component DLLS:
**C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2005
**C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2008
**C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2012
**C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2014
*Object DLLS:
**C:\Program Files\Melissa DATA\DQT\DQS\32_bit
**C:\Program Files\Melissa DATA\DQT\DQS\64_bit

==How do I enable On-Premise Global Verify?==
;Answer:
:Please make sure that you have a valid license key that has the local processing enabled. Otherwise the on-premise settings in advanced configuration settings screen will not be visible. You need to set the countries that you want to be processed through locally, the other countries that is not selected will be processed through the Global Verify web service. Please make sure your datafile structures is correct and all datafiles is present, otherwise the dll may crash or reject your settings. When everything is set you can now enter the path for the root folder of your data files into the data path field. You can test to see if you have everything set correctly by pressing test configuration. The tester will report any issues that it finds with your setup. Please contact technical support if you are still having issues with your setup and we will gladly help you out.

==How come I can't process less than 100 records for SmartMover NCOA?==
;Answer:
:USPS regulations state we cannot process NCOA for files less than 100 records. In adherence to the new regulations, SmartMover now checks the first batch to see if it contains less than 100 records. If the batch is less than 100 records we will reject the batch and return an error message. SmartMover will interrupt the processing after processing begins. Please contact your sales representative if you have any questions or concerns regarding this change.

==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]

==How do I make Excel Source Drivers work?==
;Answer:
:The version of the OLE Drivers must match your Office edition (32bit vs 64bit) in your project properties. If you have 32bit Office, click Project then Properties. Under configuration properties, click "debugging" and set "Run64BitRunTime" to False. If you have 64bit Office then set "Run64BitRunTime" to True.

==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/Visual Studio Is Your Components Supported in?==
;Answer:
:Melissa Data currently supports 2008, 2012, and 2014 versions of SQL Server. We also provide components for SQL Server 2005 as part of the SSIS Installation, however, it is no longer supported. Certain Microsoft SQL Server version are supported by specific Microsoft Visual Studio versions for our components.

*Microsoft SQL Server 2014 - Microsoft Visual Studio 2013
*Microsoft SQL Server 2012 - Microsoft Visual Studio 2010/2012
*Microsoft SQL Server 2010 - Microsoft Visual Studio 2008
*Microsoft SQL Server 2008 - Microsoft Visual Studio 2005
[[Category:FAQ]]
[[Category:SSIS:Data Quality Components]]

FAQ:SSIS:Data Quality Components

2016-02-04T00:04:20Z

Oscar: /* What is affected during an install or upgrade */

[[SSIS:Data Quality Components|← SSIS:Data Quality Components]]
{{CustomTOC}}

==What is affected during an install or upgrade==
;Answer:
:By default the data is stored at this path: C:\Program Files\Melissa DATA\DQT\Data

*Sample Projects is located
** C:\Program Files\Melissa DATA\DQT\DQS\Samples
*DLLS:
**C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2005
**C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2008
**C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2012
**C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2014

==How do I enable On-Premise Global Verify?==
;Answer:
:Please make sure that you have a valid license key that has the local processing enabled. Otherwise the on-premise settings in advanced configuration settings screen will not be visible. You need to set the countries that you want to be processed through locally, the other countries that is not selected will be processed through the Global Verify web service. Please make sure your datafile structures is correct and all datafiles is present, otherwise the dll may crash or reject your settings. When everything is set you can now enter the path for the root folder of your data files into the data path field. You can test to see if you have everything set correctly by pressing test configuration. The tester will report any issues that it finds with your setup. Please contact technical support if you are still having issues with your setup and we will gladly help you out.

==How come I can't process less than 100 records for SmartMover NCOA?==
;Answer:
:USPS regulations state we cannot process NCOA for files less than 100 records. In adherence to the new regulations, SmartMover now checks the first batch to see if it contains less than 100 records. If the batch is less than 100 records we will reject the batch and return an error message. SmartMover will interrupt the processing after processing begins. Please contact your sales representative if you have any questions or concerns regarding this change.

==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]

==How do I make Excel Source Drivers work?==
;Answer:
:The version of the OLE Drivers must match your Office edition (32bit vs 64bit) in your project properties. If you have 32bit Office, click Project then Properties. Under configuration properties, click "debugging" and set "Run64BitRunTime" to False. If you have 64bit Office then set "Run64BitRunTime" to True.

==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/Visual Studio Is Your Components Supported in?==
;Answer:
:Melissa Data currently supports 2008, 2012, and 2014 versions of SQL Server. We also provide components for SQL Server 2005 as part of the SSIS Installation, however, it is no longer supported. Certain Microsoft SQL Server version are supported by specific Microsoft Visual Studio versions for our components.

*Microsoft SQL Server 2014 - Microsoft Visual Studio 2013
*Microsoft SQL Server 2012 - Microsoft Visual Studio 2010/2012
*Microsoft SQL Server 2010 - Microsoft Visual Studio 2008
*Microsoft SQL Server 2008 - Microsoft Visual Studio 2005
[[Category:FAQ]]
[[Category:SSIS:Data Quality Components]]

FAQ:SSIS:Data Quality Components

2016-02-04T00:03:44Z

Oscar:

[[SSIS:Data Quality Components|← SSIS:Data Quality Components]]
{{CustomTOC}}

==What is affected during an install or upgrade==
;Answer:
:By default the data is stored at this path: C:\Program Files\Melissa DATA\DQT\Data
Sample Code is located : C:\Program Files\Melissa DATA\DQT\DQS\Samples
DLLS: C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2005
C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2008
C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2012
C:\Program Files\Melissa DATA\DQT\DQS\SSIS_2014

==How do I enable On-Premise Global Verify?==
;Answer:
:Please make sure that you have a valid license key that has the local processing enabled. Otherwise the on-premise settings in advanced configuration settings screen will not be visible. You need to set the countries that you want to be processed through locally, the other countries that is not selected will be processed through the Global Verify web service. Please make sure your datafile structures is correct and all datafiles is present, otherwise the dll may crash or reject your settings. When everything is set you can now enter the path for the root folder of your data files into the data path field. You can test to see if you have everything set correctly by pressing test configuration. The tester will report any issues that it finds with your setup. Please contact technical support if you are still having issues with your setup and we will gladly help you out.

==How come I can't process less than 100 records for SmartMover NCOA?==
;Answer:
:USPS regulations state we cannot process NCOA for files less than 100 records. In adherence to the new regulations, SmartMover now checks the first batch to see if it contains less than 100 records. If the batch is less than 100 records we will reject the batch and return an error message. SmartMover will interrupt the processing after processing begins. Please contact your sales representative if you have any questions or concerns regarding this change.

==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]

==How do I make Excel Source Drivers work?==
;Answer:
:The version of the OLE Drivers must match your Office edition (32bit vs 64bit) in your project properties. If you have 32bit Office, click Project then Properties. Under configuration properties, click "debugging" and set "Run64BitRunTime" to False. If you have 64bit Office then set "Run64BitRunTime" to True.

==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/Visual Studio Is Your Components Supported in?==
;Answer:
:Melissa Data currently supports 2008, 2012, and 2014 versions of SQL Server. We also provide components for SQL Server 2005 as part of the SSIS Installation, however, it is no longer supported. Certain Microsoft SQL Server version are supported by specific Microsoft Visual Studio versions for our components.

*Microsoft SQL Server 2014 - Microsoft Visual Studio 2013
*Microsoft SQL Server 2012 - Microsoft Visual Studio 2010/2012
*Microsoft SQL Server 2010 - Microsoft Visual Studio 2008
*Microsoft SQL Server 2008 - Microsoft Visual Studio 2005
[[Category:FAQ]]
[[Category:SSIS:Data Quality Components]]

FAQ:SSIS:Known Issues

2016-01-13T20:50:07Z

Oscar: /* SSIS: Global Verify License Issue */

[[SSIS:Data Quality Components|← SSIS:Data Quality Components]]
{{CustomTOC}}
==SSIS 5.4: MatchUp Unhandled Exception Error==
We discovered an issue with the 64bit Matchup DLL in SSIS, which hangs with unhandled exception error when operated in 64bit mode with a certain data-type and modified pre-canned matchcode.
;Resolution
As a workaround, you can use the 32bit version by switching run64bitruntime to false in project properties or use parameters to force 32-bit mode in DTExec.
Matchup should run fine in 32bit mode.

==SSIS 5.4: MatchUp Mapping Addressline 4-8 Issue==
Users that update to 5.4 may experience mapping issues with address 4-8 in Matchup Component.
;Resolution
Updating to patch build 2683 will resolve this issue. Please download from
ftp://ftp.melissadata.com/updates/DQC-web.exe

==SSIS 5.3/5.4: MatchUp Expired Database without Updates==
Users who do not update to MatchUp build 2683 will experience an expired database (actual expiration date is 2015-12-29).
;Resolution
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:SSIS:Data Quality Components|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.

==SSIS 5.3: Global Verify On Premise Crashes==
SSIS will crash when specific combination of visual studio and SSIS causes runtime to use only 32 bit processing. For now, we officially only support 64 bit version processing. You can check if the correct behavior is exhibited, by opening process manager and see if there are both 32bit and 64bit DtsDebugHost is running. If only 32bit is running, we do not officially support 32bit run time. We are working hard to provide a stable 32bit runtime DLL.

;Resolution
This is a Microsoft SSIS known issue as they left out DTExec 64-bit in SSDT-BI/2013, we provide both 64bit and 32bit dlls but 32bit DLL is not officially supported by Melissa Data. As of current our object is meant to be run in 64bit runtime. If during processing SSIS uses only the 32bit instead of the 64bit. Please the below help links and try the solutions provided by Microsoft. We will notify when we have 32bit version ready.
*https://support.microsoft.com/en-us/kb/2881285
*https://connect.microsoft.com/VisualStudio/feedback/details/1041486/debugging-ssis-package-opens-32-bit-dtsdebughost-exe-instead-of-64-bit-and-causes-errors

;Known Setup Issues:
Installed SSIS 2012, Using Visual Studio 2012, Visual Studio 2010 Installed
*Behavior: Uses two 32bit DtsdebugHost and crashes

;Known Working:
Installed SSIS 2012, Installed Visual Studio 2012, Using Visual Studio 2010
*Behavior: Working
Installed SSIS 2014, Using Visual Studio 2013
*Behavior: Working

==SSIS 5.3: Global Verify License Issue==
SSIS will complain about license Issue.

;Resolution
Fixed in patched build 2575. Please download from FTP
ftp://ftp.melissadata.com/Updates/DQC-web.exe

==SSIS: Matchup UK Matchcode Not Saving==
When using the Matchup UK Matchcodes, it doesn't save the UK matchcodes.

;Resolution
Fixed in patched build 2575. Please re-download from the notification email, it has been updated with the fix.
ftp://ftp.melissadata.com/Updates/DQC-web.exe

==Upgrading Global Address with Global Name, Phone, and Email==
Current users of the Global Verify Component who are only subscribed to Global Address Check and want to upgrade using either Global Name, Phone or Email, are required to re-install the components and enter their new license string in the installer.

[[File:SSIS_Install_License.png|link=]]

Upgrading your license in the Component GUI using '''File''' > '''Advanced Configuration''' will currently not work.
Alternatively, you can manually change your license string by editing the GlobalVerify.SSIS.Config under:

<pre>
C:\ProgramData\Melissa DATA\GlobalVerify
</pre>

and replace your license string for this entry:

<pre>
<License>ENTER NEW LICENSE HERE</License>
</pre>

Save the file and open SQL Server Data Tools. You should now be able to use the Global Verify Component with Global Address, Name, Phone and Email.

==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:Known Issues

2016-01-13T20:49:57Z

Oscar: /* SSIS: Global Verify On Premise Crashes */

[[SSIS:Data Quality Components|← SSIS:Data Quality Components]]
{{CustomTOC}}
==SSIS 5.4: MatchUp Unhandled Exception Error==
We discovered an issue with the 64bit Matchup DLL in SSIS, which hangs with unhandled exception error when operated in 64bit mode with a certain data-type and modified pre-canned matchcode.
;Resolution
As a workaround, you can use the 32bit version by switching run64bitruntime to false in project properties or use parameters to force 32-bit mode in DTExec.
Matchup should run fine in 32bit mode.

==SSIS 5.4: MatchUp Mapping Addressline 4-8 Issue==
Users that update to 5.4 may experience mapping issues with address 4-8 in Matchup Component.
;Resolution
Updating to patch build 2683 will resolve this issue. Please download from
ftp://ftp.melissadata.com/updates/DQC-web.exe

==SSIS 5.3/5.4: MatchUp Expired Database without Updates==
Users who do not update to MatchUp build 2683 will experience an expired database (actual expiration date is 2015-12-29).
;Resolution
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:SSIS:Data Quality Components|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.

==SSIS 5.3: Global Verify On Premise Crashes==
SSIS will crash when specific combination of visual studio and SSIS causes runtime to use only 32 bit processing. For now, we officially only support 64 bit version processing. You can check if the correct behavior is exhibited, by opening process manager and see if there are both 32bit and 64bit DtsDebugHost is running. If only 32bit is running, we do not officially support 32bit run time. We are working hard to provide a stable 32bit runtime DLL.

;Resolution
This is a Microsoft SSIS known issue as they left out DTExec 64-bit in SSDT-BI/2013, we provide both 64bit and 32bit dlls but 32bit DLL is not officially supported by Melissa Data. As of current our object is meant to be run in 64bit runtime. If during processing SSIS uses only the 32bit instead of the 64bit. Please the below help links and try the solutions provided by Microsoft. We will notify when we have 32bit version ready.
*https://support.microsoft.com/en-us/kb/2881285
*https://connect.microsoft.com/VisualStudio/feedback/details/1041486/debugging-ssis-package-opens-32-bit-dtsdebughost-exe-instead-of-64-bit-and-causes-errors

;Known Setup Issues:
Installed SSIS 2012, Using Visual Studio 2012, Visual Studio 2010 Installed
*Behavior: Uses two 32bit DtsdebugHost and crashes

;Known Working:
Installed SSIS 2012, Installed Visual Studio 2012, Using Visual Studio 2010
*Behavior: Working
Installed SSIS 2014, Using Visual Studio 2013
*Behavior: Working

==SSIS: Global Verify License Issue==
SSIS will complain about license Issue.

;Resolution
Fixed in patched build 2575. Please download from FTP
ftp://ftp.melissadata.com/Updates/DQC-web.exe

==SSIS: Matchup UK Matchcode Not Saving==
When using the Matchup UK Matchcodes, it doesn't save the UK matchcodes.

;Resolution
Fixed in patched build 2575. Please re-download from the notification email, it has been updated with the fix.
ftp://ftp.melissadata.com/Updates/DQC-web.exe

==Upgrading Global Address with Global Name, Phone, and Email==
Current users of the Global Verify Component who are only subscribed to Global Address Check and want to upgrade using either Global Name, Phone or Email, are required to re-install the components and enter their new license string in the installer.

[[File:SSIS_Install_License.png|link=]]

Upgrading your license in the Component GUI using '''File''' > '''Advanced Configuration''' will currently not work.
Alternatively, you can manually change your license string by editing the GlobalVerify.SSIS.Config under:

<pre>
C:\ProgramData\Melissa DATA\GlobalVerify
</pre>

and replace your license string for this entry:

<pre>
<License>ENTER NEW LICENSE HERE</License>
</pre>

Save the file and open SQL Server Data Tools. You should now be able to use the Global Verify Component with Global Address, Name, Phone and Email.

==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:Known Issues

2016-01-13T20:49:48Z

Oscar: /* SSIS: MatchUp Expired Database without Updates */

[[SSIS:Data Quality Components|← SSIS:Data Quality Components]]
{{CustomTOC}}
==SSIS 5.4: MatchUp Unhandled Exception Error==
We discovered an issue with the 64bit Matchup DLL in SSIS, which hangs with unhandled exception error when operated in 64bit mode with a certain data-type and modified pre-canned matchcode.
;Resolution
As a workaround, you can use the 32bit version by switching run64bitruntime to false in project properties or use parameters to force 32-bit mode in DTExec.
Matchup should run fine in 32bit mode.

==SSIS 5.4: MatchUp Mapping Addressline 4-8 Issue==
Users that update to 5.4 may experience mapping issues with address 4-8 in Matchup Component.
;Resolution
Updating to patch build 2683 will resolve this issue. Please download from
ftp://ftp.melissadata.com/updates/DQC-web.exe

==SSIS 5.3/5.4: MatchUp Expired Database without Updates==
Users who do not update to MatchUp build 2683 will experience an expired database (actual expiration date is 2015-12-29).
;Resolution
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:SSIS:Data Quality Components|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.

==SSIS: Global Verify On Premise Crashes==
SSIS will crash when specific combination of visual studio and SSIS causes runtime to use only 32 bit processing. For now, we officially only support 64 bit version processing. You can check if the correct behavior is exhibited, by opening process manager and see if there are both 32bit and 64bit DtsDebugHost is running. If only 32bit is running, we do not officially support 32bit run time. We are working hard to provide a stable 32bit runtime DLL.

;Resolution
This is a Microsoft SSIS known issue as they left out DTExec 64-bit in SSDT-BI/2013, we provide both 64bit and 32bit dlls but 32bit DLL is not officially supported by Melissa Data. As of current our object is meant to be run in 64bit runtime. If during processing SSIS uses only the 32bit instead of the 64bit. Please the below help links and try the solutions provided by Microsoft. We will notify when we have 32bit version ready.
*https://support.microsoft.com/en-us/kb/2881285
*https://connect.microsoft.com/VisualStudio/feedback/details/1041486/debugging-ssis-package-opens-32-bit-dtsdebughost-exe-instead-of-64-bit-and-causes-errors

;Known Setup Issues:
Installed SSIS 2012, Using Visual Studio 2012, Visual Studio 2010 Installed
*Behavior: Uses two 32bit DtsdebugHost and crashes

;Known Working:
Installed SSIS 2012, Installed Visual Studio 2012, Using Visual Studio 2010
*Behavior: Working
Installed SSIS 2014, Using Visual Studio 2013
*Behavior: Working

==SSIS: Global Verify License Issue==
SSIS will complain about license Issue.

;Resolution
Fixed in patched build 2575. Please download from FTP
ftp://ftp.melissadata.com/Updates/DQC-web.exe

==SSIS: Matchup UK Matchcode Not Saving==
When using the Matchup UK Matchcodes, it doesn't save the UK matchcodes.

;Resolution
Fixed in patched build 2575. Please re-download from the notification email, it has been updated with the fix.
ftp://ftp.melissadata.com/Updates/DQC-web.exe

==Upgrading Global Address with Global Name, Phone, and Email==
Current users of the Global Verify Component who are only subscribed to Global Address Check and want to upgrade using either Global Name, Phone or Email, are required to re-install the components and enter their new license string in the installer.

[[File:SSIS_Install_License.png|link=]]

Upgrading your license in the Component GUI using '''File''' > '''Advanced Configuration''' will currently not work.
Alternatively, you can manually change your license string by editing the GlobalVerify.SSIS.Config under:

<pre>
C:\ProgramData\Melissa DATA\GlobalVerify
</pre>

and replace your license string for this entry:

<pre>
<License>ENTER NEW LICENSE HERE</License>
</pre>

Save the file and open SQL Server Data Tools. You should now be able to use the Global Verify Component with Global Address, Name, Phone and Email.

==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:Known Issues

2016-01-13T20:49:12Z

Oscar: /* SSIS: Personator Not Verifying */

[[SSIS:Data Quality Components|← SSIS:Data Quality Components]]
{{CustomTOC}}
==SSIS 5.4: MatchUp Unhandled Exception Error==
We discovered an issue with the 64bit Matchup DLL in SSIS, which hangs with unhandled exception error when operated in 64bit mode with a certain data-type and modified pre-canned matchcode.
;Resolution
As a workaround, you can use the 32bit version by switching run64bitruntime to false in project properties or use parameters to force 32-bit mode in DTExec.
Matchup should run fine in 32bit mode.

==SSIS 5.4: MatchUp Mapping Addressline 4-8 Issue==
Users that update to 5.4 may experience mapping issues with address 4-8 in Matchup Component.
;Resolution
Updating to patch build 2683 will resolve this issue. Please download from
ftp://ftp.melissadata.com/updates/DQC-web.exe

==SSIS: MatchUp Expired Database without Updates==
Users who do not update to MatchUp build 2683 will experience an expired database (actual expiration date is 2015-12-29).
;Resolution
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:SSIS:Data Quality Components|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.

==SSIS: Global Verify On Premise Crashes==
SSIS will crash when specific combination of visual studio and SSIS causes runtime to use only 32 bit processing. For now, we officially only support 64 bit version processing. You can check if the correct behavior is exhibited, by opening process manager and see if there are both 32bit and 64bit DtsDebugHost is running. If only 32bit is running, we do not officially support 32bit run time. We are working hard to provide a stable 32bit runtime DLL.

;Resolution
This is a Microsoft SSIS known issue as they left out DTExec 64-bit in SSDT-BI/2013, we provide both 64bit and 32bit dlls but 32bit DLL is not officially supported by Melissa Data. As of current our object is meant to be run in 64bit runtime. If during processing SSIS uses only the 32bit instead of the 64bit. Please the below help links and try the solutions provided by Microsoft. We will notify when we have 32bit version ready.
*https://support.microsoft.com/en-us/kb/2881285
*https://connect.microsoft.com/VisualStudio/feedback/details/1041486/debugging-ssis-package-opens-32-bit-dtsdebughost-exe-instead-of-64-bit-and-causes-errors

;Known Setup Issues:
Installed SSIS 2012, Using Visual Studio 2012, Visual Studio 2010 Installed
*Behavior: Uses two 32bit DtsdebugHost and crashes

;Known Working:
Installed SSIS 2012, Installed Visual Studio 2012, Using Visual Studio 2010
*Behavior: Working
Installed SSIS 2014, Using Visual Studio 2013
*Behavior: Working

==SSIS: Global Verify License Issue==
SSIS will complain about license Issue.

;Resolution
Fixed in patched build 2575. Please download from FTP
ftp://ftp.melissadata.com/Updates/DQC-web.exe

==SSIS: Matchup UK Matchcode Not Saving==
When using the Matchup UK Matchcodes, it doesn't save the UK matchcodes.

;Resolution
Fixed in patched build 2575. Please re-download from the notification email, it has been updated with the fix.
ftp://ftp.melissadata.com/Updates/DQC-web.exe

==Upgrading Global Address with Global Name, Phone, and Email==
Current users of the Global Verify Component who are only subscribed to Global Address Check and want to upgrade using either Global Name, Phone or Email, are required to re-install the components and enter their new license string in the installer.

[[File:SSIS_Install_License.png|link=]]

Upgrading your license in the Component GUI using '''File''' > '''Advanced Configuration''' will currently not work.
Alternatively, you can manually change your license string by editing the GlobalVerify.SSIS.Config under:

<pre>
C:\ProgramData\Melissa DATA\GlobalVerify
</pre>

and replace your license string for this entry:

<pre>
<License>ENTER NEW LICENSE HERE</License>
</pre>

Save the file and open SQL Server Data Tools. You should now be able to use the Global Verify Component with Global Address, Name, Phone and Email.

==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:Known Issues

2016-01-13T20:48:19Z

Oscar:

[[SSIS:Data Quality Components|← SSIS:Data Quality Components]]
{{CustomTOC}}
==SSIS 5.4: MatchUp Unhandled Exception Error==
We discovered an issue with the 64bit Matchup DLL in SSIS, which hangs with unhandled exception error when operated in 64bit mode with a certain data-type and modified pre-canned matchcode.
;Resolution
As a workaround, you can use the 32bit version by switching run64bitruntime to false in project properties or use parameters to force 32-bit mode in DTExec.
Matchup should run fine in 32bit mode.

==SSIS 5.4: MatchUp Mapping Addressline 4-8 Issue==
Users that update to 5.4 may experience mapping issues with address 4-8 in Matchup Component.
;Resolution
Updating to patch build 2683 will resolve this issue. Please download from
ftp://ftp.melissadata.com/updates/DQC-web.exe

==SSIS: MatchUp Expired Database without Updates==
Users who do not update to MatchUp build 2683 will experience an expired database (actual expiration date is 2015-12-29).
;Resolution
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:SSIS:Data Quality Components|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.

==SSIS: Global Verify On Premise Crashes==
SSIS will crash when specific combination of visual studio and SSIS causes runtime to use only 32 bit processing. For now, we officially only support 64 bit version processing. You can check if the correct behavior is exhibited, by opening process manager and see if there are both 32bit and 64bit DtsDebugHost is running. If only 32bit is running, we do not officially support 32bit run time. We are working hard to provide a stable 32bit runtime DLL.

;Resolution
This is a Microsoft SSIS known issue as they left out DTExec 64-bit in SSDT-BI/2013, we provide both 64bit and 32bit dlls but 32bit DLL is not officially supported by Melissa Data. As of current our object is meant to be run in 64bit runtime. If during processing SSIS uses only the 32bit instead of the 64bit. Please the below help links and try the solutions provided by Microsoft. We will notify when we have 32bit version ready.
*https://support.microsoft.com/en-us/kb/2881285
*https://connect.microsoft.com/VisualStudio/feedback/details/1041486/debugging-ssis-package-opens-32-bit-dtsdebughost-exe-instead-of-64-bit-and-causes-errors

;Known Setup Issues:
Installed SSIS 2012, Using Visual Studio 2012, Visual Studio 2010 Installed
*Behavior: Uses two 32bit DtsdebugHost and crashes

;Known Working:
Installed SSIS 2012, Installed Visual Studio 2012, Using Visual Studio 2010
*Behavior: Working
Installed SSIS 2014, Using Visual Studio 2013
*Behavior: Working

==SSIS: Global Verify License Issue==
SSIS will complain about license Issue.

;Resolution
Fixed in patched build 2575. Please download from FTP
ftp://ftp.melissadata.com/Updates/DQC-web.exe

==SSIS: Matchup UK Matchcode Not Saving==
When using the Matchup UK Matchcodes, it doesn't save the UK matchcodes.

;Resolution
Fixed in patched build 2575. Please re-download from the notification email, it has been updated with the fix.
ftp://ftp.melissadata.com/Updates/DQC-web.exe

==SSIS: Personator Not Verifying==
When using the Personator Verify option, no verify result codes are coming back.
ftp://ftp.melissadata.com/Updates/DQC-web.exe

;Resolution
Fixed in patched build 2575. Please redownload from the notification email, it has been updated with the fix.

==Upgrading Global Address with Global Name, Phone, and Email==
Current users of the Global Verify Component who are only subscribed to Global Address Check and want to upgrade using either Global Name, Phone or Email, are required to re-install the components and enter their new license string in the installer.

[[File:SSIS_Install_License.png|link=]]

Upgrading your license in the Component GUI using '''File''' > '''Advanced Configuration''' will currently not work.
Alternatively, you can manually change your license string by editing the GlobalVerify.SSIS.Config under:

<pre>
C:\ProgramData\Melissa DATA\GlobalVerify
</pre>

and replace your license string for this entry:

<pre>
<License>ENTER NEW LICENSE HERE</License>
</pre>

Save the file and open SQL Server Data Tools. You should now be able to use the Global Verify Component with Global Address, Name, Phone and Email.

==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:Component Specific

2016-01-13T20:44:36Z

Oscar: /* Global Verify Component FAQ */

FAQ:SSIS:Component Specific

2016-01-13T20:44:28Z

Oscar: /* Personator Component FAQ */

==Matchup Component FAQ==
Basics:
*[[MatchUp Object:Best Practices|MatchUp Best Practices]]
*[[MatchUp Object:Matchcode Components|Matchcode Components]]
*[[MatchUp Object:Matchcode Mapping|Matchcode Mapping]]
*[[MatchUp Object:Deduping Methods|Deduping Methods]]
*[[MatchUp Object:International Users|International Users]]

Advanced:
*[[MatchUp Object:Matchcode Combinations|Matchcode Combinations]]
*[[MatchUp Object:Blank Field Matching|Blank Field Matching]]
*[[MatchUp Object:Optimizing Matchcodes|Optimizing Matchcodes]]
*[[MatchUp Object:Advanced Algorithms|Information on Advanced Algorithms]]

==Contact Verify Component FAQ==
*[[Address Object:Best Practices|Increasing Address Processing Speeds]]

==Personator Component FAQ==
*[[FAQ:Personator|Personator General FAQ]]

==Profiler Component FAQ==
==Global Verify Component FAQ==
*[[Global Address Verification:FAQ|Global Address Verification FAQ]]

==SmartMover Component FAQ==
==Fuzzy Match Component FAQ==
==IP Locator Component FAQ==
==Property Component FAQ==

FAQ:SSIS:Component Specific

2016-01-13T20:44:15Z

Oscar: /* Global Verify Component FAQ */

==Matchup Component FAQ==
Basics:
*[[MatchUp Object:Best Practices|MatchUp Best Practices]]
*[[MatchUp Object:Matchcode Components|Matchcode Components]]
*[[MatchUp Object:Matchcode Mapping|Matchcode Mapping]]
*[[MatchUp Object:Deduping Methods|Deduping Methods]]
*[[MatchUp Object:International Users|International Users]]

Advanced:
*[[MatchUp Object:Matchcode Combinations|Matchcode Combinations]]
*[[MatchUp Object:Blank Field Matching|Blank Field Matching]]
*[[MatchUp Object:Optimizing Matchcodes|Optimizing Matchcodes]]
*[[MatchUp Object:Advanced Algorithms|Information on Advanced Algorithms]]

==Contact Verify Component FAQ==
*[[Address Object:Best Practices|Increasing Address Processing Speeds]]

==Personator Component FAQ==
*[[FAQ:Personator|Personator FAQ]]

==Profiler Component FAQ==
==Global Verify Component FAQ==
*[[Global Address Verification:FAQ|Global Address Verification FAQ]]

==SmartMover Component FAQ==
==Fuzzy Match Component FAQ==
==IP Locator Component FAQ==
==Property Component FAQ==

FAQ:SSIS:Component Specific

2016-01-13T20:44:02Z

Oscar: /* Global Verify Component FAQ */

==Matchup Component FAQ==
Basics:
*[[MatchUp Object:Best Practices|MatchUp Best Practices]]
*[[MatchUp Object:Matchcode Components|Matchcode Components]]
*[[MatchUp Object:Matchcode Mapping|Matchcode Mapping]]
*[[MatchUp Object:Deduping Methods|Deduping Methods]]
*[[MatchUp Object:International Users|International Users]]

Advanced:
*[[MatchUp Object:Matchcode Combinations|Matchcode Combinations]]
*[[MatchUp Object:Blank Field Matching|Blank Field Matching]]
*[[MatchUp Object:Optimizing Matchcodes|Optimizing Matchcodes]]
*[[MatchUp Object:Advanced Algorithms|Information on Advanced Algorithms]]

==Contact Verify Component FAQ==
*[[Address Object:Best Practices|Increasing Address Processing Speeds]]

==Personator Component FAQ==
*[[FAQ:Personator|Personator FAQ]]

==Profiler Component FAQ==
==Global Verify Component FAQ==
*[[Global Address Verification:FAQ|Global Address Verification]]

==SmartMover Component FAQ==
==Fuzzy Match Component FAQ==
==IP Locator Component FAQ==
==Property Component FAQ==

FAQ:SSIS:Component Specific

2016-01-13T20:41:14Z

Oscar: /* Personator Component FAQ */

==Matchup Component FAQ==
Basics:
*[[MatchUp Object:Best Practices|MatchUp Best Practices]]
*[[MatchUp Object:Matchcode Components|Matchcode Components]]
*[[MatchUp Object:Matchcode Mapping|Matchcode Mapping]]
*[[MatchUp Object:Deduping Methods|Deduping Methods]]
*[[MatchUp Object:International Users|International Users]]

Advanced:
*[[MatchUp Object:Matchcode Combinations|Matchcode Combinations]]
*[[MatchUp Object:Blank Field Matching|Blank Field Matching]]
*[[MatchUp Object:Optimizing Matchcodes|Optimizing Matchcodes]]
*[[MatchUp Object:Advanced Algorithms|Information on Advanced Algorithms]]

==Contact Verify Component FAQ==
*[[Address Object:Best Practices|Increasing Address Processing Speeds]]

==Personator Component FAQ==
*[[FAQ:Personator|Personator FAQ]]

==Profiler Component FAQ==
==Global Verify Component FAQ==
==SmartMover Component FAQ==
==Fuzzy Match Component FAQ==
==IP Locator Component FAQ==
==Property Component FAQ==

FAQ:SSIS:Component Specific

2016-01-13T20:38:35Z

Oscar: /* Matchup Component FAQ */

==Matchup Component FAQ==
Basics:
*[[MatchUp Object:Best Practices|MatchUp Best Practices]]
*[[MatchUp Object:Matchcode Components|Matchcode Components]]
*[[MatchUp Object:Matchcode Mapping|Matchcode Mapping]]
*[[MatchUp Object:Deduping Methods|Deduping Methods]]
*[[MatchUp Object:International Users|International Users]]

Advanced:
*[[MatchUp Object:Matchcode Combinations|Matchcode Combinations]]
*[[MatchUp Object:Blank Field Matching|Blank Field Matching]]
*[[MatchUp Object:Optimizing Matchcodes|Optimizing Matchcodes]]
*[[MatchUp Object:Advanced Algorithms|Information on Advanced Algorithms]]

==Contact Verify Component FAQ==
*[[Address Object:Best Practices|Increasing Address Processing Speeds]]

==Personator Component FAQ==
==Profiler Component FAQ==
==Global Verify Component FAQ==
==SmartMover Component FAQ==
==Fuzzy Match Component FAQ==
==IP Locator Component FAQ==
==Property Component FAQ==

FAQ:SSIS:Component Specific

2016-01-13T20:38:26Z

Oscar: /* Contact Verify Component FAQ */

==Matchup Component FAQ==
Basics:
*[[MatchUp Object:Best Practices|MatchUp Object Best Practices]]
*[[MatchUp Object:Matchcode Components|Matchcode Components]]
*[[MatchUp Object:Matchcode Mapping|Matchcode Mapping]]
*[[MatchUp Object:Deduping Methods|Deduping Methods]]
*[[MatchUp Object:International Users|International Users]]

Advanced:
*[[MatchUp Object:Matchcode Combinations|Matchcode Combinations]]
*[[MatchUp Object:Blank Field Matching|Blank Field Matching]]
*[[MatchUp Object:Optimizing Matchcodes|Optimizing Matchcodes]]
*[[MatchUp Object:Advanced Algorithms|Information on Advanced Algorithms]]

==Contact Verify Component FAQ==
*[[Address Object:Best Practices|Increasing Address Processing Speeds]]

==Personator Component FAQ==
==Profiler Component FAQ==
==Global Verify Component FAQ==
==SmartMover Component FAQ==
==Fuzzy Match Component FAQ==
==IP Locator Component FAQ==
==Property Component FAQ==

FAQ:SSIS:Component Specific

2016-01-13T20:38:02Z

Oscar: /* Contact Verify Component FAQ */

==Matchup Component FAQ==
Basics:
*[[MatchUp Object:Best Practices|MatchUp Object Best Practices]]
*[[MatchUp Object:Matchcode Components|Matchcode Components]]
*[[MatchUp Object:Matchcode Mapping|Matchcode Mapping]]
*[[MatchUp Object:Deduping Methods|Deduping Methods]]
*[[MatchUp Object:International Users|International Users]]

Advanced:
*[[MatchUp Object:Matchcode Combinations|Matchcode Combinations]]
*[[MatchUp Object:Blank Field Matching|Blank Field Matching]]
*[[MatchUp Object:Optimizing Matchcodes|Optimizing Matchcodes]]
*[[MatchUp Object:Advanced Algorithms|Information on Advanced Algorithms]]

==Contact Verify Component FAQ==
*[[Address Object:Best Practices|Address Best Practices]]

==Personator Component FAQ==
==Profiler Component FAQ==
==Global Verify Component FAQ==
==SmartMover Component FAQ==
==Fuzzy Match Component FAQ==
==IP Locator Component FAQ==
==Property Component FAQ==

FAQ:SSIS:Component Specific

2016-01-13T20:36:07Z

Oscar: /* Matchup Component FAQ */

==Matchup Component FAQ==
Basics:
*[[MatchUp Object:Best Practices|MatchUp Object Best Practices]]
*[[MatchUp Object:Matchcode Components|Matchcode Components]]
*[[MatchUp Object:Matchcode Mapping|Matchcode Mapping]]
*[[MatchUp Object:Deduping Methods|Deduping Methods]]
*[[MatchUp Object:International Users|International Users]]

Advanced:
*[[MatchUp Object:Matchcode Combinations|Matchcode Combinations]]
*[[MatchUp Object:Blank Field Matching|Blank Field Matching]]
*[[MatchUp Object:Optimizing Matchcodes|Optimizing Matchcodes]]
*[[MatchUp Object:Advanced Algorithms|Information on Advanced Algorithms]]

==Contact Verify Component FAQ==
==Personator Component FAQ==
==Profiler Component FAQ==
==Global Verify Component FAQ==
==SmartMover Component FAQ==
==Fuzzy Match Component FAQ==
==IP Locator Component FAQ==
==Property Component FAQ==

FAQ:SSIS:Component Specific

2016-01-13T20:35:24Z

Oscar: /* Matchup Component FAQ */

FAQ:SSIS:Component Specific

2016-01-13T20:34:52Z

Oscar: /* Matchup Component FAQ */

==Matchup Component FAQ==
*[[MatchUp Object:Best Practices|MatchUp Object Best Practices]]
*[[MatchUp Object:Matchcode Components|Matchcode Components]]
*[[MatchUp Object:Matchcode Mapping|Matchcode Mapping]]
*[[MatchUp Object:Deduping Methods|Deduping Methods]]
*[[MatchUp Object:International Users|International Users]]

==Contact Verify Component FAQ==
==Personator Component FAQ==
==Profiler Component FAQ==
==Global Verify Component FAQ==
==SmartMover Component FAQ==
==Fuzzy Match Component FAQ==
==IP Locator Component FAQ==
==Property Component FAQ==

SSIS:Data Quality Components

2016-01-13T20:33:59Z

Oscar:

__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 November 2015
<br>Build 5.4
*[[Build History:SSIS:Data Quality Components|Build History]]
|BodyCol2=
<h3>Notices</h3>
*[[FAQ:SSIS:Known Issues|Known Issues]]
}}
|-
|valign="top" width="50%" style="padding-right:8px;"|
{{ProductLeft
|Color=green
|Image=[[File:MediumTile_Essentials.png|link=]]
|Body=
<h3>Basics</h3>
*[[SSIS:Best Practices|SSIS Best Practices]]
*[[SSIS:Installation|Installation]]
<h3>FAQ</h3>
*[[FAQ:SSIS:Data Quality Components|Data Quality Components for SSIS]]
*[[FAQ:SSIS:Data Type Conversions|Data Type Conversions]]
*[[FAQ:SSIS:Component Specific|Component Specific FAQ & Optimizations]]
<h3>Tutorial Videos</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>
*[[SSIS:Reference|DQC SSIS Online Reference]]
*[[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 Code Details#SSIS Data Quality Components|SSIS DQC Result Codes]]
}}
|}

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

SSIS:Data Quality Components

2016-01-13T20:33:49Z

Oscar:

__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 November 2015
<br>Build 5.4
*[[Build History:SSIS:Data Quality Components|Build History]]
|BodyCol2=
<h3>Notices</h3>
*[[FAQ:SSIS:Known Issues|Known Issues]]
}}
|-
|valign="top" width="50%" style="padding-right:8px;"|
{{ProductLeft
|Color=green
|Image=[[File:MediumTile_Essentials.png|link=]]
|Body=
<h3>Basics</h3>
*[[SSIS:Best Practices|SSIS Best Practices]]
*[[SSIS:Installation|Installation]]
<h3>FAQ</h3>
*[[FAQ:SSIS:Data Quality Components|Data Quality Components for SSIS]]
*[[FAQ:SSIS:Data Type Conversions|Data Type Conversions]]
*[[FAQ:SSIS:Component Specific|Component Specific FAQ & Optmizations]]
<h3>Tutorial Videos</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>
*[[SSIS:Reference|DQC SSIS Online Reference]]
*[[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 Code Details#SSIS Data Quality Components|SSIS DQC Result Codes]]
}}
|}

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

FAQ:SSIS:Component Specific

2016-01-13T20:33:13Z

Oscar: Created page with "==Matchup Component FAQ== ==Contact Verify Component FAQ== ==Personator Component FAQ== ==Profiler Component FAQ== ==Global Verify Component FAQ== ==SmartMover Component FAQ==..."

==Matchup Component FAQ==
==Contact Verify Component FAQ==
==Personator Component FAQ==
==Profiler Component FAQ==
==Global Verify Component FAQ==
==SmartMover Component FAQ==
==Fuzzy Match Component FAQ==
==IP Locator Component FAQ==
==Property Component FAQ==

SSIS:Data Quality Components

2016-01-13T20:32:23Z

Oscar:

__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 November 2015
<br>Build 5.4
*[[Build History:SSIS:Data Quality Components|Build History]]
|BodyCol2=
<h3>Notices</h3>
*[[FAQ:SSIS:Known Issues|Known Issues]]
}}
|-
|valign="top" width="50%" style="padding-right:8px;"|
{{ProductLeft
|Color=green
|Image=[[File:MediumTile_Essentials.png|link=]]
|Body=
<h3>Basics</h3>
*[[SSIS:Best Practices|SSIS Best Practices]]
*[[SSIS:Installation|Installation]]
<h3>FAQ</h3>
*[[FAQ:SSIS:Data Quality Components|Data Quality Components for SSIS]]
*[[FAQ:SSIS:Data Type Conversions|Data Type Conversions]]
*[[FAQ:SSIS:Component Specific|Component Specific]]
<h3>Tutorial Videos</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>
*[[SSIS:Reference|DQC SSIS Online Reference]]
*[[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 Code Details#SSIS Data Quality Components|SSIS DQC Result Codes]]
}}
|}

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

SSIS:Data Quality Components

2016-01-13T20:32:02Z

Oscar:

__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 November 2015
<br>Build 5.4
*[[Build History:SSIS:Data Quality Components|Build History]]
|BodyCol2=
<h3>Notices</h3>
*[[FAQ:SSIS:Known Issues|Known Issues]]
}}
|-
|valign="top" width="50%" style="padding-right:8px;"|
{{ProductLeft
|Color=green
|Image=[[File:MediumTile_Essentials.png|link=]]
|Body=
<h3>Basics</h3>
*[[SSIS:Best Practices|SSIS Best Practices]]
*[[SSIS:Installation|Installation]]
<h3>FAQ</h3>
*[[FAQ:SSIS:Data Quality Components|Data Quality Components for SSIS]]
*[[FAQ:SSIS:Data Type Conversions|Data Type Conversions]]
*[[FAQ:SSIS:Component Specific FAQ|Component Specific]]
<h3>Tutorial Videos</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>
*[[SSIS:Reference|DQC SSIS Online Reference]]
*[[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 Code Details#SSIS Data Quality Components|SSIS DQC Result Codes]]
}}
|}

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

FAQ:SSIS:Component Specific FAQ

2016-01-13T20:31:30Z

Oscar:

FAQ:SSIS:Component Specific FAQ

2016-01-13T20:29:05Z

Oscar: Created page with "==Matchup Component FAQ=="

==Matchup Component FAQ==

SSIS:Data Quality Components

2016-01-13T20:27:34Z

Oscar:

__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 November 2015
<br>Build 5.4
*[[Build History:SSIS:Data Quality Components|Build History]]
|BodyCol2=
<h3>Notices</h3>
*[[FAQ:SSIS:Known Issues|Known Issues]]
}}
|-
|valign="top" width="50%" style="padding-right:8px;"|
{{ProductLeft
|Color=green
|Image=[[File:MediumTile_Essentials.png|link=]]
|Body=
<h3>Basics</h3>
*[[SSIS:Best Practices|SSIS Best Practices]]
*[[SSIS:Installation|Installation]]
<h3>FAQ</h3>
*[[FAQ:SSIS:Data Quality Components|Data Quality Components for SSIS]]
*[[FAQ:SSIS:Data Type Conversions|Data Type Conversions]]
*[[FAQ:SSIS:Component Specific FAQ|Component Specific FAQ]]
<h3>Tutorial Videos</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>
*[[SSIS:Reference|DQC SSIS Online Reference]]
*[[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 Code Details#SSIS Data Quality Components|SSIS DQC Result Codes]]
}}
|}

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

Build History:SSIS:Data Quality Components

2016-01-04T23:53:22Z

Oscar: /* Build 5.4 */

[[SSIS:Data Quality Components|← SSIS:Data Quality Components]]
{{CustomTOC}}

==Build 5.4==
;''Released November 2015''
:''Patch Released January 2016 [Build 2683]''

;Contact Verification Component
:Version: 1.0.1.2683
:Address Object Build: 2575
:Name Object Build: 2613
:Phone Object Build: 2613
:Email Object Build: 2554
:Geocoder Object Build: 2670
:MatchUp Object Build: 2628
:IpLocator Object Build: 2615
:Database Date: 10/15/2015

:;Changes

:*Community edition now requires a community edition license key, rather than no license key

;Personator Component
:Version: 1.0.0.2683

:;Changes

:*Fixed an issue with transaction size

;SmartMover Component
:Version: 1.0.1.2683

:;Changes

:*Transaction size setting locked to 100 records in accordance to USPS regulations

;Fuzzy Matching Component
:Version 2.0.0.2683

:;Changes

:*None

;MatchUp Component
:Version 2.2.0.2683

:;Changes

:*International Matchup capabilities now added to Matchup Component
:*Community edition now requires a community edition license key, rather than no license key
:*Fixed an issue where users would experience field mapping issues in a matchcode (address 4-8)
:*Fixed database expiration issue

;Global Verify Component
:Version 2.0.0.2683
:Global Address Object Build: 2620 (32bit), 2600 (64bit)
:;Changes

:*Added new On-Premise component
:*New processing modes: Webservice, On-Premise, Hybrid. WS sends all records to webservice, on-premise sends all records to the local object, and hybrid sends specified records to webservice OR the local object.

;IP Locator Component
:Version 1.0.0.2683

:;Changes

:*None

;Property Component
:Version 1.0.0.2683

:;Changes

:*None

;Profiler Component
:Version 1.0.0.2683

:;Changes

:*Community edition now requires a community edition license key, rather than no license key

==Build 5.3==
''Released August 2015''

;Contact Verification Component
:Version: 1.0.1.2626
:Address Object Build: 2613
:Name Object Build: 2613
:Phone Object Build: 2613
:Email Object Build: 2554
:Geocoder Object Build: 2615
:MatchUp Object Build: 2564
:IpLocator Object Build: 2554
:Database Date: 7/15/2015

:;Changes

:*Added more result codes to the output result filter

;Personator Component
:Version: 1.0.0.2626

:;Changes

:*Fixed a problem where the "Verify" action was not being sent
:*Fixed a problem where the Personator window would crash under certain circumstances
:*Added more result codes to the output result filter

;SmartMover Component
:Version: 1.0.1.2626

:;Changes

:*Files with less than 100 records will not be processed as per USPS regulations

;Fuzzy Matching Component
:Version 2.0.0.2626

:;Changes

:*Fixed spelling error in output tab

;MatchUp Component
:Version 2.2.0.2626

:;Changes

:*Fixed an issue where matchcodes could not use (UK) data types
:*Fixed an issue where DT_Numeric data types could not have a precision value greater than scale value
:*Fixed an issue where the advanced survivorship would crash the component in certain circumstances
:*Fixed several spelling mistakes

;Global Verify Component
:Version 2.0.0.2626
:Global Address Object Build: 2620 (32bit), 2600 (64bit)
:;Changes

:*Added new On-Premise component
:*With a proper license string, users can now verify global data on their machine rather than web service
:*Fixed various issues with On-Premise mode

;IP Locator Component
:Version 1.0.0.2626

:;Changes

:*None

;Property Component
:Version 1.0.0.2626

:;Changes

:*None

;Profiler Component
:Version 1.0.0.2626

:;Changes

:*None

==Build 5.2==
''Released May 2015''

;Contact Verification Component
:Version: 1.0.1.2575
:Address Object Build: 2554
:Name Object Build: 2554
:Phone Object Build: 2554
:Email Object Build: 2554
:Geocoder Object Build: 2554
:MatchUp Object Build: 2554
:IpLocator Object Build: 2554
:Database Date: 4/15/2015

:;Changes

:*fixed "Decimal" option unselectable in "Default Lat/Long Column Type"

;Personator Component
:Version: 1.0.0.2575

:;Changes

:*Personator restriction fixes and GUI changes.
:*Move confidence option now has "Loose" and "Strict" options.

;SmartMover Component
:Version: 1.0.1.2575

:;Changes

:*None

;Fuzzy Matching Component
:Version 2.0.0.2575

:;Changes

:*None

;MatchUp Component
:Version 2.2.0.2575

:;Changes

:*fixed MatchCode Editor swap crash

;Global Verify Component
:Version 2.0.0.2575

:;Changes

:*Fixed a few German translations and spelling
:*German localization for GV.
:*Global Email interface changes.
:*Output filter ES23 description update

;IP Locator Component
:Version 1.0.0.2575

:;Changes

:*None

;Property Component
:Version 1.0.0.2575

:;Changes

:*None

;Profiler Component
:Version 1.0.0.2575

:;Changes

:*Added InferredColumnType column.
:*Fixed issue where users would get error if they didn’t specify any output fields on the passthrough/results pin.

==Build 5.1==
''Released February 2015''

;Contact Verification Component
:Version: 1.0.1.2503
:Address Object Build: 2502
:Name Object Build: 2502
:Phone Object Build: 2502
:Email Object Build: 2502
:Geocoder Object Build: 2502
:MatchUp Object Build: 2408
:IpLocator Object Build: 2502
:Database Date: 1/15/2015

:;Changes

:*Fixed behavior of ‘Output Filter’ tab’s Filter controls in some instances.

;Personator Component
:Version: 1.0.0.2499

:;Changes

:*Added Demographics fields.

;SmartMover Component
:Version: 1.0.1.2503

:;Changes

:*None

;Fuzzy Matching Component
:Version 2.0.0.2502

:;Changes

:*None

;MatchUp Component
:Version 2.2.0.2499

:;Changes

:*Fixed issue where slow machines would crash if user changed tabs quickly during GUI startup.

;Global Verify Component
:Version 2.0.0.2503

:;Changes

:*Dialog not saving changes in rare instances.
:*User is now allowed to pass Advanced Configuration test with only some activated web services.
:*‘Default Lat/Long Column Type’ would not display checkmark if the selection was ‘Decimal’

;IP Locator Component
:Version 1.0.0.2503

:;Changes

:*None

;Property Component
:Version 1.0.0.2499

:;Changes

:*None

;Profiler Component
:Version 1.0.0.2503

:;Changes

:*Fixed issue where users would get error if they didn’t specify any output fields on the passthrough/results pin.

==Build 4.4==
''Released November 2014''
;Contact Verification Component
:Version: 1.0.1.2449
:Address Object Build: 2431
:Name Object Build: 2431
:Phone Object Build: 2431
:Email Object Build: 2431
:Geocoder Object Build: 2441
:MatchUp Object Build: 2441
:IpLocator Object Build: 2441
:Database Date: 10/15/2014

:;Changes

:*None

;Personator Component
:Version: 1.0.0.2449

:;Changes

:*Fixed a problem where output filters were not being saved
:*Improved performance when saving the component

;SmartMover Component
:Version: 1.0.1.2449

:;Changes

:*Fixed a backwards compatibility issue
:*Fixed a problem where output filters were not being saved

;Fuzzy Matching Component
:Version 2.0.0.2449

:;Changes

:*None

;MatchUp Component
:Version 2.2.0.2449

:;Changes

:*None

;Global Verify Component
:Version 2.0.0.2449

:;Changes

:*Added new Name Tab and Functionalities
:*Added new Phone Tab and Functionalities
:*Added new Email Tab and Functionalities

;IP Locator Component
:Version 1.0.0.2449

:;Changes

:*None

;Property Component
:Version 1.0.0.2449

:;Changes

:*New Component

==Build 4.3==
''Released August 2014''
;Contact Verification Component
:Version: 1.0.1. 2419
:Address Object Build: 2381
:Name Object Build: 2381
:Phone Object Build: 2381
:Email Object Build: 2381
:Geocoder Object Build: 2408
:MatchUp Object Build: 2408
:Database Date: 07/15/2014

:;Changes
:*Changed option "Peroform WS Lookup" for Email Check to default to false.
:*Fixed problem with Result Codes when switching from Community Edition to Full Version

;Personator Component
:Version: 1.0.0.2419

:;Changes
:*Fixed a problem where some options were disabled in certain conditions.
:*Pass-through data types now match exactly what is input.

;SmartMover Component
:Version: 1.0.1.2419

:;Changes
:*GUI modifications
:*Component now communicates with new v3 version of SmartMover web service.
:*Added Canadian Change of Address processing via Canadian SmartMover web service.

;Fuzzy Matching Component
:Version 2.0.0.2419

:;Changes
:*Added SSIS data type descriptions to ‘Options’ drop-down menu.

;MatchUp Component
:Version: 2.2.0.2419

:;Changes
:*Added SSIS data type descriptions to ‘Options’ drop-down menu.

;IPLocator Component
:Version: 2.2.0.2419

:;Changes
:*Initial Release

==Build 4.2==
''Released May 2014''

;Compatibility Summary
:The following DLLs are now being compiled in Visual Studio 2012:
:*Address Object
:*Name Object
:*Phone Object
:*Email Object
:*Geocoder Object
:*MatchUp Object

:This requires the installation of the 2012 Visual C++ Redistributable which is included in the SSIS Installation.

;Installer
:The Setup will automatically install 2012 Visual C++ Redistributable (x86 and x64) for compatibility with VS 2012 Compiled DLLs.

;Contact Verification Component
:Version: 1.0.1. 2368
:Address Object Build: 2362
:Name Object Build: 2362
:Phone Object Build: 2362
:Email Object Build: 2362
:Geocoder Object Build: 2362
:MatchUp Object Build: 2362
:Database Date: 04/15/2014

:;Changes

:*Added additional option in the configuration file for DisableAddressSwapping. This option can be set to true in order to permanently disable the swapping of AddressLine1 and AddressLine2.

;Personator Component
:Version: 1.0.0. 2368

:;Changes

:*Added ‘Freeform’ input address field option.
:*Set maximum output field size to 255 instead of 256 (particularly problematic for Excel).
:*Actions were sometimes unselected automatically.
:*Pass-through columns were not always passing through data.
:*Changed verification so that outputting just a result code is not an error.
:*Pass-through's ‘Select All’ button didn’t always work.
:*No default was selected for the Append options.

;MatchUp Component
:Version: 2.2.0. 2368

:;Changes

:*Fixed a problem with date-distance matchcodes; dates with trailing spaces weren’t properly parsed.
:*Fixed a problem with ‘Join with Spaces’ not properly working with an Intersection Lookup source.
:*Fixed a problem where editing survivorship output column size was not getting saved.
:*Survivorship mode ‘Average’ wasn’t working correctly for integers.

;Global Verify Component
:Version: 2.2.0. 2368

:;Changes

:*Added Delivery Lines Option in the GUI for outputting the complete Global Mailing address in AddressLines 1 - 8.

==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]]

Build History:SSIS:Data Quality Components

2016-01-04T23:53:09Z

Oscar: /* Build 5.4 */

[[SSIS:Data Quality Components|← SSIS:Data Quality Components]]
{{CustomTOC}}

==Build 5.4==
;''Released November 2015''
:''Patch Released January 2016 [Build 2683]''

;Contact Verification Component
:Version: 1.0.1.2683
:Address Object Build: 2575
:Name Object Build: 2613
:Phone Object Build: 2613
:Email Object Build: 2554
:Geocoder Object Build: 2670
:MatchUp Object Build: 2628
:IpLocator Object Build: 2615
:Database Date: 10/15/2015

:;Changes

:*Community edition now requires a community edition license key, rather than no license key

;Personator Component
:Version: 1.0.0.2683

:;Changes

:*Fixed an issue with transaction size

;SmartMover Component
:Version: 1.0.1.2683

:;Changes

:*Transaction size setting locked to 100 records in accordance to USPS regulations

;Fuzzy Matching Component
:Version 2.0.0.2683

:;Changes

:*None

;MatchUp Component
:Version 2.2.0.2683

:;Changes

:*International Matchup capabilities now added to Matchup Component
:*Community edition now requires a community edition license key, rather than no license key\
:*Fixed an issue where users would experience field mapping issues in a matchcode (address 4-8)
:*Fixed database expiration issue

;Global Verify Component
:Version 2.0.0.2683
:Global Address Object Build: 2620 (32bit), 2600 (64bit)
:;Changes

:*Added new On-Premise component
:*New processing modes: Webservice, On-Premise, Hybrid. WS sends all records to webservice, on-premise sends all records to the local object, and hybrid sends specified records to webservice OR the local object.

;IP Locator Component
:Version 1.0.0.2683

:;Changes

:*None

;Property Component
:Version 1.0.0.2683

:;Changes

:*None

;Profiler Component
:Version 1.0.0.2683

:;Changes

:*Community edition now requires a community edition license key, rather than no license key

==Build 5.3==
''Released August 2015''

;Contact Verification Component
:Version: 1.0.1.2626
:Address Object Build: 2613
:Name Object Build: 2613
:Phone Object Build: 2613
:Email Object Build: 2554
:Geocoder Object Build: 2615
:MatchUp Object Build: 2564
:IpLocator Object Build: 2554
:Database Date: 7/15/2015

:;Changes

:*Added more result codes to the output result filter

;Personator Component
:Version: 1.0.0.2626

:;Changes

:*Fixed a problem where the "Verify" action was not being sent
:*Fixed a problem where the Personator window would crash under certain circumstances
:*Added more result codes to the output result filter

;SmartMover Component
:Version: 1.0.1.2626

:;Changes

:*Files with less than 100 records will not be processed as per USPS regulations

;Fuzzy Matching Component
:Version 2.0.0.2626

:;Changes

:*Fixed spelling error in output tab

;MatchUp Component
:Version 2.2.0.2626

:;Changes

:*Fixed an issue where matchcodes could not use (UK) data types
:*Fixed an issue where DT_Numeric data types could not have a precision value greater than scale value
:*Fixed an issue where the advanced survivorship would crash the component in certain circumstances
:*Fixed several spelling mistakes

;Global Verify Component
:Version 2.0.0.2626
:Global Address Object Build: 2620 (32bit), 2600 (64bit)
:;Changes

:*Added new On-Premise component
:*With a proper license string, users can now verify global data on their machine rather than web service
:*Fixed various issues with On-Premise mode

;IP Locator Component
:Version 1.0.0.2626

:;Changes

:*None

;Property Component
:Version 1.0.0.2626

:;Changes

:*None

;Profiler Component
:Version 1.0.0.2626

:;Changes

:*None

==Build 5.2==
''Released May 2015''

;Contact Verification Component
:Version: 1.0.1.2575
:Address Object Build: 2554
:Name Object Build: 2554
:Phone Object Build: 2554
:Email Object Build: 2554
:Geocoder Object Build: 2554
:MatchUp Object Build: 2554
:IpLocator Object Build: 2554
:Database Date: 4/15/2015

:;Changes

:*fixed "Decimal" option unselectable in "Default Lat/Long Column Type"

;Personator Component
:Version: 1.0.0.2575

:;Changes

:*Personator restriction fixes and GUI changes.
:*Move confidence option now has "Loose" and "Strict" options.

;SmartMover Component
:Version: 1.0.1.2575

:;Changes

:*None

;Fuzzy Matching Component
:Version 2.0.0.2575

:;Changes

:*None

;MatchUp Component
:Version 2.2.0.2575

:;Changes

:*fixed MatchCode Editor swap crash

;Global Verify Component
:Version 2.0.0.2575

:;Changes

:*Fixed a few German translations and spelling
:*German localization for GV.
:*Global Email interface changes.
:*Output filter ES23 description update

;IP Locator Component
:Version 1.0.0.2575

:;Changes

:*None

;Property Component
:Version 1.0.0.2575

:;Changes

:*None

;Profiler Component
:Version 1.0.0.2575

:;Changes

:*Added InferredColumnType column.
:*Fixed issue where users would get error if they didn’t specify any output fields on the passthrough/results pin.

==Build 5.1==
''Released February 2015''

;Contact Verification Component
:Version: 1.0.1.2503
:Address Object Build: 2502
:Name Object Build: 2502
:Phone Object Build: 2502
:Email Object Build: 2502
:Geocoder Object Build: 2502
:MatchUp Object Build: 2408
:IpLocator Object Build: 2502
:Database Date: 1/15/2015

:;Changes

:*Fixed behavior of ‘Output Filter’ tab’s Filter controls in some instances.

;Personator Component
:Version: 1.0.0.2499

:;Changes

:*Added Demographics fields.

;SmartMover Component
:Version: 1.0.1.2503

:;Changes

:*None

;Fuzzy Matching Component
:Version 2.0.0.2502

:;Changes

:*None

;MatchUp Component
:Version 2.2.0.2499

:;Changes

:*Fixed issue where slow machines would crash if user changed tabs quickly during GUI startup.

;Global Verify Component
:Version 2.0.0.2503

:;Changes

:*Dialog not saving changes in rare instances.
:*User is now allowed to pass Advanced Configuration test with only some activated web services.
:*‘Default Lat/Long Column Type’ would not display checkmark if the selection was ‘Decimal’

;IP Locator Component
:Version 1.0.0.2503

:;Changes

:*None

;Property Component
:Version 1.0.0.2499

:;Changes

:*None

;Profiler Component
:Version 1.0.0.2503

:;Changes

:*Fixed issue where users would get error if they didn’t specify any output fields on the passthrough/results pin.

==Build 4.4==
''Released November 2014''
;Contact Verification Component
:Version: 1.0.1.2449
:Address Object Build: 2431
:Name Object Build: 2431
:Phone Object Build: 2431
:Email Object Build: 2431
:Geocoder Object Build: 2441
:MatchUp Object Build: 2441
:IpLocator Object Build: 2441
:Database Date: 10/15/2014

:;Changes

:*None

;Personator Component
:Version: 1.0.0.2449

:;Changes

:*Fixed a problem where output filters were not being saved
:*Improved performance when saving the component

;SmartMover Component
:Version: 1.0.1.2449

:;Changes

:*Fixed a backwards compatibility issue
:*Fixed a problem where output filters were not being saved

;Fuzzy Matching Component
:Version 2.0.0.2449

:;Changes

:*None

;MatchUp Component
:Version 2.2.0.2449

:;Changes

:*None

;Global Verify Component
:Version 2.0.0.2449

:;Changes

:*Added new Name Tab and Functionalities
:*Added new Phone Tab and Functionalities
:*Added new Email Tab and Functionalities

;IP Locator Component
:Version 1.0.0.2449

:;Changes

:*None

;Property Component
:Version 1.0.0.2449

:;Changes

:*New Component

==Build 4.3==
''Released August 2014''
;Contact Verification Component
:Version: 1.0.1. 2419
:Address Object Build: 2381
:Name Object Build: 2381
:Phone Object Build: 2381
:Email Object Build: 2381
:Geocoder Object Build: 2408
:MatchUp Object Build: 2408
:Database Date: 07/15/2014

:;Changes
:*Changed option "Peroform WS Lookup" for Email Check to default to false.
:*Fixed problem with Result Codes when switching from Community Edition to Full Version

;Personator Component
:Version: 1.0.0.2419

:;Changes
:*Fixed a problem where some options were disabled in certain conditions.
:*Pass-through data types now match exactly what is input.

;SmartMover Component
:Version: 1.0.1.2419

:;Changes
:*GUI modifications
:*Component now communicates with new v3 version of SmartMover web service.
:*Added Canadian Change of Address processing via Canadian SmartMover web service.

;Fuzzy Matching Component
:Version 2.0.0.2419

:;Changes
:*Added SSIS data type descriptions to ‘Options’ drop-down menu.

;MatchUp Component
:Version: 2.2.0.2419

:;Changes
:*Added SSIS data type descriptions to ‘Options’ drop-down menu.

;IPLocator Component
:Version: 2.2.0.2419

:;Changes
:*Initial Release

==Build 4.2==
''Released May 2014''

;Compatibility Summary
:The following DLLs are now being compiled in Visual Studio 2012:
:*Address Object
:*Name Object
:*Phone Object
:*Email Object
:*Geocoder Object
:*MatchUp Object

:This requires the installation of the 2012 Visual C++ Redistributable which is included in the SSIS Installation.

;Installer
:The Setup will automatically install 2012 Visual C++ Redistributable (x86 and x64) for compatibility with VS 2012 Compiled DLLs.

;Contact Verification Component
:Version: 1.0.1. 2368
:Address Object Build: 2362
:Name Object Build: 2362
:Phone Object Build: 2362
:Email Object Build: 2362
:Geocoder Object Build: 2362
:MatchUp Object Build: 2362
:Database Date: 04/15/2014

:;Changes

:*Added additional option in the configuration file for DisableAddressSwapping. This option can be set to true in order to permanently disable the swapping of AddressLine1 and AddressLine2.

;Personator Component
:Version: 1.0.0. 2368

:;Changes

:*Added ‘Freeform’ input address field option.
:*Set maximum output field size to 255 instead of 256 (particularly problematic for Excel).
:*Actions were sometimes unselected automatically.
:*Pass-through columns were not always passing through data.
:*Changed verification so that outputting just a result code is not an error.
:*Pass-through's ‘Select All’ button didn’t always work.
:*No default was selected for the Append options.

;MatchUp Component
:Version: 2.2.0. 2368

:;Changes

:*Fixed a problem with date-distance matchcodes; dates with trailing spaces weren’t properly parsed.
:*Fixed a problem with ‘Join with Spaces’ not properly working with an Intersection Lookup source.
:*Fixed a problem where editing survivorship output column size was not getting saved.
:*Survivorship mode ‘Average’ wasn’t working correctly for integers.

;Global Verify Component
:Version: 2.2.0. 2368

:;Changes

:*Added Delivery Lines Option in the GUI for outputting the complete Global Mailing address in AddressLines 1 - 8.

==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]]

FAQ:SSIS:Known Issues

2016-01-04T23:51:42Z

Oscar: /* SSIS 5.4: MatchUp Mapping Addressline 4-8 Issue */

[[SSIS:Data Quality Components|← SSIS:Data Quality Components]]
{{CustomTOC}}

==SSIS 5.4: MatchUp Mapping Addressline 4-8 Issue==
Users that update to 5.4 may experience mapping issues with address 4-8 in Matchup Component.
;Resolution
Updating to patch build 2683 will resolve this issue. Please download from
ftp://ftp.melissadata.com/updates/DQC-web.exe

==SSIS: MatchUp Expired Database without Updates==
Users who do not update to MatchUp build 2683 will experience an expired database (actual expiration date is 2015-12-29).
;Resolution
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:SSIS:Data Quality Components|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.

==SSIS: Global Verify On Premise Crashes==
SSIS will crash when specific combination of visual studio and SSIS causes runtime to use only 32 bit processing. For now, we officially only support 64 bit version processing. You can check if the correct behavior is exhibited, by opening process manager and see if there are both 32bit and 64bit DtsDebugHost is running. If only 32bit is running, we do not officially support 32bit run time. We are working hard to provide a stable 32bit runtime DLL.

;Resolution
This is a Microsoft SSIS known issue as they left out DTExec 64-bit in SSDT-BI/2013, we provide both 64bit and 32bit dlls but 32bit DLL is not officially supported by Melissa Data. As of current our object is meant to be run in 64bit runtime. If during processing SSIS uses only the 32bit instead of the 64bit. Please the below help links and try the solutions provided by Microsoft. We will notify when we have 32bit version ready.
*https://support.microsoft.com/en-us/kb/2881285
*https://connect.microsoft.com/VisualStudio/feedback/details/1041486/debugging-ssis-package-opens-32-bit-dtsdebughost-exe-instead-of-64-bit-and-causes-errors

;Known Setup Issues:
Installed SSIS 2012, Using Visual Studio 2012, Visual Studio 2010 Installed
*Behavior: Uses two 32bit DtsdebugHost and crashes

;Known Working:
Installed SSIS 2012, Installed Visual Studio 2012, Using Visual Studio 2010
*Behavior: Working
Installed SSIS 2014, Using Visual Studio 2013
*Behavior: Working

==SSIS: Global Verify License Issue==
SSIS will complain about license Issue.

;Resolution
Fixed in patched build 2575. Please download from FTP
ftp://ftp.melissadata.com/Updates/DQC-web.exe

==SSIS: Matchup UK Matchcode Not Saving==
When using the Matchup UK Matchcodes, it doesn't save the UK matchcodes.

;Resolution
Fixed in patched build 2575. Please re-download from the notification email, it has been updated with the fix.
ftp://ftp.melissadata.com/Updates/DQC-web.exe

==SSIS: Personator Not Verifying==
When using the Personator Verify option, no verify result codes are coming back.
ftp://ftp.melissadata.com/Updates/DQC-web.exe

;Resolution
Fixed in patched build 2575. Please redownload from the notification email, it has been updated with the fix.

==Upgrading Global Address with Global Name, Phone, and Email==
Current users of the Global Verify Component who are only subscribed to Global Address Check and want to upgrade using either Global Name, Phone or Email, are required to re-install the components and enter their new license string in the installer.

[[File:SSIS_Install_License.png|link=]]

Upgrading your license in the Component GUI using '''File''' > '''Advanced Configuration''' will currently not work.
Alternatively, you can manually change your license string by editing the GlobalVerify.SSIS.Config under:

<pre>
C:\ProgramData\Melissa DATA\GlobalVerify
</pre>

and replace your license string for this entry:

<pre>
<License>ENTER NEW LICENSE HERE</License>
</pre>

Save the file and open SQL Server Data Tools. You should now be able to use the Global Verify Component with Global Address, Name, Phone and Email.

==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:Known Issues

2016-01-04T23:51:13Z

Oscar: /* SSIS 5.4: MatchUp Mapping Addressline 4-8 Issue */

[[SSIS:Data Quality Components|← SSIS:Data Quality Components]]
{{CustomTOC}}

==SSIS 5.4: MatchUp Mapping Addressline 4-8 Issue==
Users that update to 5.4 may experience mapping issues with matchcode type for address 4-8 in Matchup Component.
;Resolution
Updating to patch build 2683 will resolve this issue. Please download from
ftp://ftp.melissadata.com/updates/DQC-web.exe

==SSIS: MatchUp Expired Database without Updates==
Users who do not update to MatchUp build 2683 will experience an expired database (actual expiration date is 2015-12-29).
;Resolution
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:SSIS:Data Quality Components|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.

==SSIS: Global Verify On Premise Crashes==
SSIS will crash when specific combination of visual studio and SSIS causes runtime to use only 32 bit processing. For now, we officially only support 64 bit version processing. You can check if the correct behavior is exhibited, by opening process manager and see if there are both 32bit and 64bit DtsDebugHost is running. If only 32bit is running, we do not officially support 32bit run time. We are working hard to provide a stable 32bit runtime DLL.

;Resolution
This is a Microsoft SSIS known issue as they left out DTExec 64-bit in SSDT-BI/2013, we provide both 64bit and 32bit dlls but 32bit DLL is not officially supported by Melissa Data. As of current our object is meant to be run in 64bit runtime. If during processing SSIS uses only the 32bit instead of the 64bit. Please the below help links and try the solutions provided by Microsoft. We will notify when we have 32bit version ready.
*https://support.microsoft.com/en-us/kb/2881285
*https://connect.microsoft.com/VisualStudio/feedback/details/1041486/debugging-ssis-package-opens-32-bit-dtsdebughost-exe-instead-of-64-bit-and-causes-errors

;Known Setup Issues:
Installed SSIS 2012, Using Visual Studio 2012, Visual Studio 2010 Installed
*Behavior: Uses two 32bit DtsdebugHost and crashes

;Known Working:
Installed SSIS 2012, Installed Visual Studio 2012, Using Visual Studio 2010
*Behavior: Working
Installed SSIS 2014, Using Visual Studio 2013
*Behavior: Working

==SSIS: Global Verify License Issue==
SSIS will complain about license Issue.

;Resolution
Fixed in patched build 2575. Please download from FTP
ftp://ftp.melissadata.com/Updates/DQC-web.exe

==SSIS: Matchup UK Matchcode Not Saving==
When using the Matchup UK Matchcodes, it doesn't save the UK matchcodes.

;Resolution
Fixed in patched build 2575. Please re-download from the notification email, it has been updated with the fix.
ftp://ftp.melissadata.com/Updates/DQC-web.exe

==SSIS: Personator Not Verifying==
When using the Personator Verify option, no verify result codes are coming back.
ftp://ftp.melissadata.com/Updates/DQC-web.exe

;Resolution
Fixed in patched build 2575. Please redownload from the notification email, it has been updated with the fix.

==Upgrading Global Address with Global Name, Phone, and Email==
Current users of the Global Verify Component who are only subscribed to Global Address Check and want to upgrade using either Global Name, Phone or Email, are required to re-install the components and enter their new license string in the installer.

[[File:SSIS_Install_License.png|link=]]

Upgrading your license in the Component GUI using '''File''' > '''Advanced Configuration''' will currently not work.
Alternatively, you can manually change your license string by editing the GlobalVerify.SSIS.Config under:

<pre>
C:\ProgramData\Melissa DATA\GlobalVerify
</pre>

and replace your license string for this entry:

<pre>
<License>ENTER NEW LICENSE HERE</License>
</pre>

Save the file and open SQL Server Data Tools. You should now be able to use the Global Verify Component with Global Address, Name, Phone and Email.

==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:Known Issues

2016-01-04T23:50:26Z

Oscar: /* SSIS 5.4: MatchUp Mapping Addressline 4-8 Issue */

[[SSIS:Data Quality Components|← SSIS:Data Quality Components]]
{{CustomTOC}}

==SSIS 5.4: MatchUp Mapping Addressline 4-8 Issue==
Users that update to 5.4 experience issue with matchcode type mapping with address 4-8.
;Resolution
Updating to patch build 2683 will resolve this issue. Please download from
ftp://ftp.melissadata.com/updates/DQC-web.exe

==SSIS: MatchUp Expired Database without Updates==
Users who do not update to MatchUp build 2683 will experience an expired database (actual expiration date is 2015-12-29).
;Resolution
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:SSIS:Data Quality Components|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.

==SSIS: Global Verify On Premise Crashes==
SSIS will crash when specific combination of visual studio and SSIS causes runtime to use only 32 bit processing. For now, we officially only support 64 bit version processing. You can check if the correct behavior is exhibited, by opening process manager and see if there are both 32bit and 64bit DtsDebugHost is running. If only 32bit is running, we do not officially support 32bit run time. We are working hard to provide a stable 32bit runtime DLL.

;Resolution
This is a Microsoft SSIS known issue as they left out DTExec 64-bit in SSDT-BI/2013, we provide both 64bit and 32bit dlls but 32bit DLL is not officially supported by Melissa Data. As of current our object is meant to be run in 64bit runtime. If during processing SSIS uses only the 32bit instead of the 64bit. Please the below help links and try the solutions provided by Microsoft. We will notify when we have 32bit version ready.
*https://support.microsoft.com/en-us/kb/2881285
*https://connect.microsoft.com/VisualStudio/feedback/details/1041486/debugging-ssis-package-opens-32-bit-dtsdebughost-exe-instead-of-64-bit-and-causes-errors

;Known Setup Issues:
Installed SSIS 2012, Using Visual Studio 2012, Visual Studio 2010 Installed
*Behavior: Uses two 32bit DtsdebugHost and crashes

;Known Working:
Installed SSIS 2012, Installed Visual Studio 2012, Using Visual Studio 2010
*Behavior: Working
Installed SSIS 2014, Using Visual Studio 2013
*Behavior: Working

==SSIS: Global Verify License Issue==
SSIS will complain about license Issue.

;Resolution
Fixed in patched build 2575. Please download from FTP
ftp://ftp.melissadata.com/Updates/DQC-web.exe

==SSIS: Matchup UK Matchcode Not Saving==
When using the Matchup UK Matchcodes, it doesn't save the UK matchcodes.

;Resolution
Fixed in patched build 2575. Please re-download from the notification email, it has been updated with the fix.
ftp://ftp.melissadata.com/Updates/DQC-web.exe

==SSIS: Personator Not Verifying==
When using the Personator Verify option, no verify result codes are coming back.
ftp://ftp.melissadata.com/Updates/DQC-web.exe

;Resolution
Fixed in patched build 2575. Please redownload from the notification email, it has been updated with the fix.

==Upgrading Global Address with Global Name, Phone, and Email==
Current users of the Global Verify Component who are only subscribed to Global Address Check and want to upgrade using either Global Name, Phone or Email, are required to re-install the components and enter their new license string in the installer.

[[File:SSIS_Install_License.png|link=]]

Upgrading your license in the Component GUI using '''File''' > '''Advanced Configuration''' will currently not work.
Alternatively, you can manually change your license string by editing the GlobalVerify.SSIS.Config under:

<pre>
C:\ProgramData\Melissa DATA\GlobalVerify
</pre>

and replace your license string for this entry:

<pre>
<License>ENTER NEW LICENSE HERE</License>
</pre>

Save the file and open SQL Server Data Tools. You should now be able to use the Global Verify Component with Global Address, Name, Phone and Email.

==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:Known Issues

2016-01-04T23:50:17Z

Oscar: /* SSIS 5.4: MatchUp Mapping Address 4-8 Issue */

[[SSIS:Data Quality Components|← SSIS:Data Quality Components]]
{{CustomTOC}}

==SSIS 5.4: MatchUp Mapping Addressline 4-8 Issue==
Users that update to 5.4 experience issue with matchcode type mapping with address 4-8.
;Resolution
Updating to patch build 2683 will resolve this issue. Please download from
ftp://ftp.melissadata.com/updates/DQC-web.exe

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.

==SSIS: MatchUp Expired Database without Updates==
Users who do not update to MatchUp build 2683 will experience an expired database (actual expiration date is 2015-12-29).
;Resolution
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:SSIS:Data Quality Components|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.

==SSIS: Global Verify On Premise Crashes==
SSIS will crash when specific combination of visual studio and SSIS causes runtime to use only 32 bit processing. For now, we officially only support 64 bit version processing. You can check if the correct behavior is exhibited, by opening process manager and see if there are both 32bit and 64bit DtsDebugHost is running. If only 32bit is running, we do not officially support 32bit run time. We are working hard to provide a stable 32bit runtime DLL.

;Resolution
This is a Microsoft SSIS known issue as they left out DTExec 64-bit in SSDT-BI/2013, we provide both 64bit and 32bit dlls but 32bit DLL is not officially supported by Melissa Data. As of current our object is meant to be run in 64bit runtime. If during processing SSIS uses only the 32bit instead of the 64bit. Please the below help links and try the solutions provided by Microsoft. We will notify when we have 32bit version ready.
*https://support.microsoft.com/en-us/kb/2881285
*https://connect.microsoft.com/VisualStudio/feedback/details/1041486/debugging-ssis-package-opens-32-bit-dtsdebughost-exe-instead-of-64-bit-and-causes-errors

;Known Setup Issues:
Installed SSIS 2012, Using Visual Studio 2012, Visual Studio 2010 Installed
*Behavior: Uses two 32bit DtsdebugHost and crashes

;Known Working:
Installed SSIS 2012, Installed Visual Studio 2012, Using Visual Studio 2010
*Behavior: Working
Installed SSIS 2014, Using Visual Studio 2013
*Behavior: Working

==SSIS: Global Verify License Issue==
SSIS will complain about license Issue.

;Resolution
Fixed in patched build 2575. Please download from FTP
ftp://ftp.melissadata.com/Updates/DQC-web.exe

==SSIS: Matchup UK Matchcode Not Saving==
When using the Matchup UK Matchcodes, it doesn't save the UK matchcodes.

;Resolution
Fixed in patched build 2575. Please re-download from the notification email, it has been updated with the fix.
ftp://ftp.melissadata.com/Updates/DQC-web.exe

==SSIS: Personator Not Verifying==
When using the Personator Verify option, no verify result codes are coming back.
ftp://ftp.melissadata.com/Updates/DQC-web.exe

;Resolution
Fixed in patched build 2575. Please redownload from the notification email, it has been updated with the fix.

==Upgrading Global Address with Global Name, Phone, and Email==
Current users of the Global Verify Component who are only subscribed to Global Address Check and want to upgrade using either Global Name, Phone or Email, are required to re-install the components and enter their new license string in the installer.

[[File:SSIS_Install_License.png|link=]]

Upgrading your license in the Component GUI using '''File''' > '''Advanced Configuration''' will currently not work.
Alternatively, you can manually change your license string by editing the GlobalVerify.SSIS.Config under:

<pre>
C:\ProgramData\Melissa DATA\GlobalVerify
</pre>

and replace your license string for this entry:

<pre>
<License>ENTER NEW LICENSE HERE</License>
</pre>

Save the file and open SQL Server Data Tools. You should now be able to use the Global Verify Component with Global Address, Name, Phone and Email.

==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:Known Issues

2016-01-04T23:49:59Z

Oscar:

[[SSIS:Data Quality Components|← SSIS:Data Quality Components]]
{{CustomTOC}}

==SSIS 5.4: MatchUp Mapping Address 4-8 Issue==
Users that update to 5.4 experience issue with matchcode type mapping with address 4-8.
;Resolution
Updating to patch build 2683 will resolve this issue. ftp://ftp.melissadata.com/updates/DQC-web.exe

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.
==SSIS: MatchUp Expired Database without Updates==
Users who do not update to MatchUp build 2683 will experience an expired database (actual expiration date is 2015-12-29).
;Resolution
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:SSIS:Data Quality Components|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.

==SSIS: Global Verify On Premise Crashes==
SSIS will crash when specific combination of visual studio and SSIS causes runtime to use only 32 bit processing. For now, we officially only support 64 bit version processing. You can check if the correct behavior is exhibited, by opening process manager and see if there are both 32bit and 64bit DtsDebugHost is running. If only 32bit is running, we do not officially support 32bit run time. We are working hard to provide a stable 32bit runtime DLL.

;Resolution
This is a Microsoft SSIS known issue as they left out DTExec 64-bit in SSDT-BI/2013, we provide both 64bit and 32bit dlls but 32bit DLL is not officially supported by Melissa Data. As of current our object is meant to be run in 64bit runtime. If during processing SSIS uses only the 32bit instead of the 64bit. Please the below help links and try the solutions provided by Microsoft. We will notify when we have 32bit version ready.
*https://support.microsoft.com/en-us/kb/2881285
*https://connect.microsoft.com/VisualStudio/feedback/details/1041486/debugging-ssis-package-opens-32-bit-dtsdebughost-exe-instead-of-64-bit-and-causes-errors

;Known Setup Issues:
Installed SSIS 2012, Using Visual Studio 2012, Visual Studio 2010 Installed
*Behavior: Uses two 32bit DtsdebugHost and crashes

;Known Working:
Installed SSIS 2012, Installed Visual Studio 2012, Using Visual Studio 2010
*Behavior: Working
Installed SSIS 2014, Using Visual Studio 2013
*Behavior: Working

==SSIS: Global Verify License Issue==
SSIS will complain about license Issue.

;Resolution
Fixed in patched build 2575. Please download from FTP
ftp://ftp.melissadata.com/Updates/DQC-web.exe

==SSIS: Matchup UK Matchcode Not Saving==
When using the Matchup UK Matchcodes, it doesn't save the UK matchcodes.

;Resolution
Fixed in patched build 2575. Please re-download from the notification email, it has been updated with the fix.
ftp://ftp.melissadata.com/Updates/DQC-web.exe

==SSIS: Personator Not Verifying==
When using the Personator Verify option, no verify result codes are coming back.
ftp://ftp.melissadata.com/Updates/DQC-web.exe

;Resolution
Fixed in patched build 2575. Please redownload from the notification email, it has been updated with the fix.

==Upgrading Global Address with Global Name, Phone, and Email==
Current users of the Global Verify Component who are only subscribed to Global Address Check and want to upgrade using either Global Name, Phone or Email, are required to re-install the components and enter their new license string in the installer.

[[File:SSIS_Install_License.png|link=]]

Upgrading your license in the Component GUI using '''File''' > '''Advanced Configuration''' will currently not work.
Alternatively, you can manually change your license string by editing the GlobalVerify.SSIS.Config under:

<pre>
C:\ProgramData\Melissa DATA\GlobalVerify
</pre>

and replace your license string for this entry:

<pre>
<License>ENTER NEW LICENSE HERE</License>
</pre>

Save the file and open SQL Server Data Tools. You should now be able to use the Global Verify Component with Global Address, Name, Phone and Email.

==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:Known Issues

2016-01-04T23:47:49Z

Oscar:

[[SSIS:Data Quality Components|← SSIS:Data Quality Components]]
{{CustomTOC}}

==SSIS: MatchUp Expired Database without Updates==
Users who do not update to MatchUp build 2683 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:SSIS:Data Quality Components|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.

==SSIS: Global Verify On Premise Crashes==
SSIS will crash when specific combination of visual studio and SSIS causes runtime to use only 32 bit processing. For now, we officially only support 64 bit version processing. You can check if the correct behavior is exhibited, by opening process manager and see if there are both 32bit and 64bit DtsDebugHost is running. If only 32bit is running, we do not officially support 32bit run time. We are working hard to provide a stable 32bit runtime DLL.

;Resolution
This is a Microsoft SSIS known issue as they left out DTExec 64-bit in SSDT-BI/2013, we provide both 64bit and 32bit dlls but 32bit DLL is not officially supported by Melissa Data. As of current our object is meant to be run in 64bit runtime. If during processing SSIS uses only the 32bit instead of the 64bit. Please the below help links and try the solutions provided by Microsoft. We will notify when we have 32bit version ready.
*https://support.microsoft.com/en-us/kb/2881285
*https://connect.microsoft.com/VisualStudio/feedback/details/1041486/debugging-ssis-package-opens-32-bit-dtsdebughost-exe-instead-of-64-bit-and-causes-errors

;Known Setup Issues:
Installed SSIS 2012, Using Visual Studio 2012, Visual Studio 2010 Installed
*Behavior: Uses two 32bit DtsdebugHost and crashes

;Known Working:
Installed SSIS 2012, Installed Visual Studio 2012, Using Visual Studio 2010
*Behavior: Working
Installed SSIS 2014, Using Visual Studio 2013
*Behavior: Working

==SSIS: Global Verify License Issue==
SSIS will complain about license Issue.

;Resolution
Fixed in patched build 2575. Please download from FTP
ftp://ftp.melissadata.com/Updates/DQC-web.exe

==SSIS: Matchup UK Matchcode Not Saving==
When using the Matchup UK Matchcodes, it doesn't save the UK matchcodes.

;Resolution
Fixed in patched build 2575. Please re-download from the notification email, it has been updated with the fix.
ftp://ftp.melissadata.com/Updates/DQC-web.exe

==SSIS: Personator Not Verifying==
When using the Personator Verify option, no verify result codes are coming back.
ftp://ftp.melissadata.com/Updates/DQC-web.exe

;Resolution
Fixed in patched build 2575. Please redownload from the notification email, it has been updated with the fix.

==Upgrading Global Address with Global Name, Phone, and Email==
Current users of the Global Verify Component who are only subscribed to Global Address Check and want to upgrade using either Global Name, Phone or Email, are required to re-install the components and enter their new license string in the installer.

[[File:SSIS_Install_License.png|link=]]

Upgrading your license in the Component GUI using '''File''' > '''Advanced Configuration''' will currently not work.
Alternatively, you can manually change your license string by editing the GlobalVerify.SSIS.Config under:

<pre>
C:\ProgramData\Melissa DATA\GlobalVerify
</pre>

and replace your license string for this entry:

<pre>
<License>ENTER NEW LICENSE HERE</License>
</pre>

Save the file and open SQL Server Data Tools. You should now be able to use the Global Verify Component with Global Address, Name, Phone and Email.

==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]]

Build History:SSIS:Data Quality Components

2016-01-04T23:46:41Z

Oscar: /* Build 5.4 */

[[SSIS:Data Quality Components|← SSIS:Data Quality Components]]
{{CustomTOC}}

==Build 5.4==
;''Released November 2015''
:''Patch Released January 2016 [Build 2683]''

;Contact Verification Component
:Version: 1.0.1.2683
:Address Object Build: 2575
:Name Object Build: 2613
:Phone Object Build: 2613
:Email Object Build: 2554
:Geocoder Object Build: 2670
:MatchUp Object Build: 2628
:IpLocator Object Build: 2615
:Database Date: 10/15/2015

:;Changes

:*Community edition now requires a community edition license key, rather than no license key

;Personator Component
:Version: 1.0.0.2683

:;Changes

:*Fixed an issue with transaction size

;SmartMover Component
:Version: 1.0.1.2683

:;Changes

:*Transaction size setting locked to 100 records in accordance to USPS regulations

;Fuzzy Matching Component
:Version 2.0.0.2683

:;Changes

:*None

;MatchUp Component
:Version 2.2.0.2683

:;Changes

:*International Matchup capabilities now added to Matchup Component
:*Community edition now requires a community edition license key, rather than no license key\
:*Fixed Matchup Component Address 4-8 mapping Issue

;Global Verify Component
:Version 2.0.0.2683
:Global Address Object Build: 2620 (32bit), 2600 (64bit)
:;Changes

:*Added new On-Premise component
:*New processing modes: Webservice, On-Premise, Hybrid. WS sends all records to webservice, on-premise sends all records to the local object, and hybrid sends specified records to webservice OR the local object.

;IP Locator Component
:Version 1.0.0.2683

:;Changes

:*None

;Property Component
:Version 1.0.0.2683

:;Changes

:*None

;Profiler Component
:Version 1.0.0.2683

:;Changes

:*Community edition now requires a community edition license key, rather than no license key

==Build 5.3==
''Released August 2015''

;Contact Verification Component
:Version: 1.0.1.2626
:Address Object Build: 2613
:Name Object Build: 2613
:Phone Object Build: 2613
:Email Object Build: 2554
:Geocoder Object Build: 2615
:MatchUp Object Build: 2564
:IpLocator Object Build: 2554
:Database Date: 7/15/2015

:;Changes

:*Added more result codes to the output result filter

;Personator Component
:Version: 1.0.0.2626

:;Changes

:*Fixed a problem where the "Verify" action was not being sent
:*Fixed a problem where the Personator window would crash under certain circumstances
:*Added more result codes to the output result filter

;SmartMover Component
:Version: 1.0.1.2626

:;Changes

:*Files with less than 100 records will not be processed as per USPS regulations

;Fuzzy Matching Component
:Version 2.0.0.2626

:;Changes

:*Fixed spelling error in output tab

;MatchUp Component
:Version 2.2.0.2626

:;Changes

:*Fixed an issue where matchcodes could not use (UK) data types
:*Fixed an issue where DT_Numeric data types could not have a precision value greater than scale value
:*Fixed an issue where the advanced survivorship would crash the component in certain circumstances
:*Fixed several spelling mistakes

;Global Verify Component
:Version 2.0.0.2626
:Global Address Object Build: 2620 (32bit), 2600 (64bit)
:;Changes

:*Added new On-Premise component
:*With a proper license string, users can now verify global data on their machine rather than web service
:*Fixed various issues with On-Premise mode

;IP Locator Component
:Version 1.0.0.2626

:;Changes

:*None

;Property Component
:Version 1.0.0.2626

:;Changes

:*None

;Profiler Component
:Version 1.0.0.2626

:;Changes

:*None

==Build 5.2==
''Released May 2015''

;Contact Verification Component
:Version: 1.0.1.2575
:Address Object Build: 2554
:Name Object Build: 2554
:Phone Object Build: 2554
:Email Object Build: 2554
:Geocoder Object Build: 2554
:MatchUp Object Build: 2554
:IpLocator Object Build: 2554
:Database Date: 4/15/2015

:;Changes

:*fixed "Decimal" option unselectable in "Default Lat/Long Column Type"

;Personator Component
:Version: 1.0.0.2575

:;Changes

:*Personator restriction fixes and GUI changes.
:*Move confidence option now has "Loose" and "Strict" options.

;SmartMover Component
:Version: 1.0.1.2575

:;Changes

:*None

;Fuzzy Matching Component
:Version 2.0.0.2575

:;Changes

:*None

;MatchUp Component
:Version 2.2.0.2575

:;Changes

:*fixed MatchCode Editor swap crash

;Global Verify Component
:Version 2.0.0.2575

:;Changes

:*Fixed a few German translations and spelling
:*German localization for GV.
:*Global Email interface changes.
:*Output filter ES23 description update

;IP Locator Component
:Version 1.0.0.2575

:;Changes

:*None

;Property Component
:Version 1.0.0.2575

:;Changes

:*None

;Profiler Component
:Version 1.0.0.2575

:;Changes

:*Added InferredColumnType column.
:*Fixed issue where users would get error if they didn’t specify any output fields on the passthrough/results pin.

==Build 5.1==
''Released February 2015''

;Contact Verification Component
:Version: 1.0.1.2503
:Address Object Build: 2502
:Name Object Build: 2502
:Phone Object Build: 2502
:Email Object Build: 2502
:Geocoder Object Build: 2502
:MatchUp Object Build: 2408
:IpLocator Object Build: 2502
:Database Date: 1/15/2015

:;Changes

:*Fixed behavior of ‘Output Filter’ tab’s Filter controls in some instances.

;Personator Component
:Version: 1.0.0.2499

:;Changes

:*Added Demographics fields.

;SmartMover Component
:Version: 1.0.1.2503

:;Changes

:*None

;Fuzzy Matching Component
:Version 2.0.0.2502

:;Changes

:*None

;MatchUp Component
:Version 2.2.0.2499

:;Changes

:*Fixed issue where slow machines would crash if user changed tabs quickly during GUI startup.

;Global Verify Component
:Version 2.0.0.2503

:;Changes

:*Dialog not saving changes in rare instances.
:*User is now allowed to pass Advanced Configuration test with only some activated web services.
:*‘Default Lat/Long Column Type’ would not display checkmark if the selection was ‘Decimal’

;IP Locator Component
:Version 1.0.0.2503

:;Changes

:*None

;Property Component
:Version 1.0.0.2499

:;Changes

:*None

;Profiler Component
:Version 1.0.0.2503

:;Changes

:*Fixed issue where users would get error if they didn’t specify any output fields on the passthrough/results pin.

==Build 4.4==
''Released November 2014''
;Contact Verification Component
:Version: 1.0.1.2449
:Address Object Build: 2431
:Name Object Build: 2431
:Phone Object Build: 2431
:Email Object Build: 2431
:Geocoder Object Build: 2441
:MatchUp Object Build: 2441
:IpLocator Object Build: 2441
:Database Date: 10/15/2014

:;Changes

:*None

;Personator Component
:Version: 1.0.0.2449

:;Changes

:*Fixed a problem where output filters were not being saved
:*Improved performance when saving the component

;SmartMover Component
:Version: 1.0.1.2449

:;Changes

:*Fixed a backwards compatibility issue
:*Fixed a problem where output filters were not being saved

;Fuzzy Matching Component
:Version 2.0.0.2449

:;Changes

:*None

;MatchUp Component
:Version 2.2.0.2449

:;Changes

:*None

;Global Verify Component
:Version 2.0.0.2449

:;Changes

:*Added new Name Tab and Functionalities
:*Added new Phone Tab and Functionalities
:*Added new Email Tab and Functionalities

;IP Locator Component
:Version 1.0.0.2449

:;Changes

:*None

;Property Component
:Version 1.0.0.2449

:;Changes

:*New Component

==Build 4.3==
''Released August 2014''
;Contact Verification Component
:Version: 1.0.1. 2419
:Address Object Build: 2381
:Name Object Build: 2381
:Phone Object Build: 2381
:Email Object Build: 2381
:Geocoder Object Build: 2408
:MatchUp Object Build: 2408
:Database Date: 07/15/2014

:;Changes
:*Changed option "Peroform WS Lookup" for Email Check to default to false.
:*Fixed problem with Result Codes when switching from Community Edition to Full Version

;Personator Component
:Version: 1.0.0.2419

:;Changes
:*Fixed a problem where some options were disabled in certain conditions.
:*Pass-through data types now match exactly what is input.

;SmartMover Component
:Version: 1.0.1.2419

:;Changes
:*GUI modifications
:*Component now communicates with new v3 version of SmartMover web service.
:*Added Canadian Change of Address processing via Canadian SmartMover web service.

;Fuzzy Matching Component
:Version 2.0.0.2419

:;Changes
:*Added SSIS data type descriptions to ‘Options’ drop-down menu.

;MatchUp Component
:Version: 2.2.0.2419

:;Changes
:*Added SSIS data type descriptions to ‘Options’ drop-down menu.

;IPLocator Component
:Version: 2.2.0.2419

:;Changes
:*Initial Release

==Build 4.2==
''Released May 2014''

;Compatibility Summary
:The following DLLs are now being compiled in Visual Studio 2012:
:*Address Object
:*Name Object
:*Phone Object
:*Email Object
:*Geocoder Object
:*MatchUp Object

:This requires the installation of the 2012 Visual C++ Redistributable which is included in the SSIS Installation.

;Installer
:The Setup will automatically install 2012 Visual C++ Redistributable (x86 and x64) for compatibility with VS 2012 Compiled DLLs.

;Contact Verification Component
:Version: 1.0.1. 2368
:Address Object Build: 2362
:Name Object Build: 2362
:Phone Object Build: 2362
:Email Object Build: 2362
:Geocoder Object Build: 2362
:MatchUp Object Build: 2362
:Database Date: 04/15/2014

:;Changes

:*Added additional option in the configuration file for DisableAddressSwapping. This option can be set to true in order to permanently disable the swapping of AddressLine1 and AddressLine2.

;Personator Component
:Version: 1.0.0. 2368

:;Changes

:*Added ‘Freeform’ input address field option.
:*Set maximum output field size to 255 instead of 256 (particularly problematic for Excel).
:*Actions were sometimes unselected automatically.
:*Pass-through columns were not always passing through data.
:*Changed verification so that outputting just a result code is not an error.
:*Pass-through's ‘Select All’ button didn’t always work.
:*No default was selected for the Append options.

;MatchUp Component
:Version: 2.2.0. 2368

:;Changes

:*Fixed a problem with date-distance matchcodes; dates with trailing spaces weren’t properly parsed.
:*Fixed a problem with ‘Join with Spaces’ not properly working with an Intersection Lookup source.
:*Fixed a problem where editing survivorship output column size was not getting saved.
:*Survivorship mode ‘Average’ wasn’t working correctly for integers.

;Global Verify Component
:Version: 2.2.0. 2368

:;Changes

:*Added Delivery Lines Option in the GUI for outputting the complete Global Mailing address in AddressLines 1 - 8.

==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]]

Build History:SSIS:Data Quality Components

2016-01-04T23:45:56Z

Oscar: /* Build 5.4 */

[[SSIS:Data Quality Components|← SSIS:Data Quality Components]]
{{CustomTOC}}

==Build 5.4==
;''Released November 2015''
:''Patch Released January 2016 [Build 2683]''

;Contact Verification Component
:Version: 1.0.1.2683
:Address Object Build: 2575
:Name Object Build: 2613
:Phone Object Build: 2613
:Email Object Build: 2554
:Geocoder Object Build: 2670
:MatchUp Object Build: 2628
:IpLocator Object Build: 2615
:Database Date: 10/15/2015

:;Changes

:*Community edition now requires a community edition license key, rather than no license key

;Personator Component
:Version: 1.0.0.2683

:;Changes

:*Fixed an issue with transaction size

;SmartMover Component
:Version: 1.0.1.2683

:;Changes

:*Transaction size setting locked to 100 records in accordance to USPS regulations

;Fuzzy Matching Component
:Version 2.0.0.2683

:;Changes

:*None

;MatchUp Component
:Version 2.2.0.2683

:;Changes

:*International Matchup capabilities now added to Matchup Component
:*Community edition now requires a community edition license key, rather than no license key\

;Global Verify Component
:Version 2.0.0.2683
:Global Address Object Build: 2620 (32bit), 2600 (64bit)
:;Changes

:*Added new On-Premise component
:*New processing modes: Webservice, On-Premise, Hybrid. WS sends all records to webservice, on-premise sends all records to the local object, and hybrid sends specified records to webservice OR the local object.

;IP Locator Component
:Version 1.0.0.2683

:;Changes

:*None

;Property Component
:Version 1.0.0.2683

:;Changes

:*None

;Profiler Component
:Version 1.0.0.2683

:;Changes

:*Community edition now requires a community edition license key, rather than no license key

==Build 5.3==
''Released August 2015''

;Contact Verification Component
:Version: 1.0.1.2626
:Address Object Build: 2613
:Name Object Build: 2613
:Phone Object Build: 2613
:Email Object Build: 2554
:Geocoder Object Build: 2615
:MatchUp Object Build: 2564
:IpLocator Object Build: 2554
:Database Date: 7/15/2015

:;Changes

:*Added more result codes to the output result filter

;Personator Component
:Version: 1.0.0.2626

:;Changes

:*Fixed a problem where the "Verify" action was not being sent
:*Fixed a problem where the Personator window would crash under certain circumstances
:*Added more result codes to the output result filter

;SmartMover Component
:Version: 1.0.1.2626

:;Changes

:*Files with less than 100 records will not be processed as per USPS regulations

;Fuzzy Matching Component
:Version 2.0.0.2626

:;Changes

:*Fixed spelling error in output tab

;MatchUp Component
:Version 2.2.0.2626

:;Changes

:*Fixed an issue where matchcodes could not use (UK) data types
:*Fixed an issue where DT_Numeric data types could not have a precision value greater than scale value
:*Fixed an issue where the advanced survivorship would crash the component in certain circumstances
:*Fixed several spelling mistakes

;Global Verify Component
:Version 2.0.0.2626
:Global Address Object Build: 2620 (32bit), 2600 (64bit)
:;Changes

:*Added new On-Premise component
:*With a proper license string, users can now verify global data on their machine rather than web service
:*Fixed various issues with On-Premise mode

;IP Locator Component
:Version 1.0.0.2626

:;Changes

:*None

;Property Component
:Version 1.0.0.2626

:;Changes

:*None

;Profiler Component
:Version 1.0.0.2626

:;Changes

:*None

==Build 5.2==
''Released May 2015''

;Contact Verification Component
:Version: 1.0.1.2575
:Address Object Build: 2554
:Name Object Build: 2554
:Phone Object Build: 2554
:Email Object Build: 2554
:Geocoder Object Build: 2554
:MatchUp Object Build: 2554
:IpLocator Object Build: 2554
:Database Date: 4/15/2015

:;Changes

:*fixed "Decimal" option unselectable in "Default Lat/Long Column Type"

;Personator Component
:Version: 1.0.0.2575

:;Changes

:*Personator restriction fixes and GUI changes.
:*Move confidence option now has "Loose" and "Strict" options.

;SmartMover Component
:Version: 1.0.1.2575

:;Changes

:*None

;Fuzzy Matching Component
:Version 2.0.0.2575

:;Changes

:*None

;MatchUp Component
:Version 2.2.0.2575

:;Changes

:*fixed MatchCode Editor swap crash

;Global Verify Component
:Version 2.0.0.2575

:;Changes

:*Fixed a few German translations and spelling
:*German localization for GV.
:*Global Email interface changes.
:*Output filter ES23 description update

;IP Locator Component
:Version 1.0.0.2575

:;Changes

:*None

;Property Component
:Version 1.0.0.2575

:;Changes

:*None

;Profiler Component
:Version 1.0.0.2575

:;Changes

:*Added InferredColumnType column.
:*Fixed issue where users would get error if they didn’t specify any output fields on the passthrough/results pin.

==Build 5.1==
''Released February 2015''

;Contact Verification Component
:Version: 1.0.1.2503
:Address Object Build: 2502
:Name Object Build: 2502
:Phone Object Build: 2502
:Email Object Build: 2502
:Geocoder Object Build: 2502
:MatchUp Object Build: 2408
:IpLocator Object Build: 2502
:Database Date: 1/15/2015

:;Changes

:*Fixed behavior of ‘Output Filter’ tab’s Filter controls in some instances.

;Personator Component
:Version: 1.0.0.2499

:;Changes

:*Added Demographics fields.

;SmartMover Component
:Version: 1.0.1.2503

:;Changes

:*None

;Fuzzy Matching Component
:Version 2.0.0.2502

:;Changes

:*None

;MatchUp Component
:Version 2.2.0.2499

:;Changes

:*Fixed issue where slow machines would crash if user changed tabs quickly during GUI startup.

;Global Verify Component
:Version 2.0.0.2503

:;Changes

:*Dialog not saving changes in rare instances.
:*User is now allowed to pass Advanced Configuration test with only some activated web services.
:*‘Default Lat/Long Column Type’ would not display checkmark if the selection was ‘Decimal’

;IP Locator Component
:Version 1.0.0.2503

:;Changes

:*None

;Property Component
:Version 1.0.0.2499

:;Changes

:*None

;Profiler Component
:Version 1.0.0.2503

:;Changes

:*Fixed issue where users would get error if they didn’t specify any output fields on the passthrough/results pin.

==Build 4.4==
''Released November 2014''
;Contact Verification Component
:Version: 1.0.1.2449
:Address Object Build: 2431
:Name Object Build: 2431
:Phone Object Build: 2431
:Email Object Build: 2431
:Geocoder Object Build: 2441
:MatchUp Object Build: 2441
:IpLocator Object Build: 2441
:Database Date: 10/15/2014

:;Changes

:*None

;Personator Component
:Version: 1.0.0.2449

:;Changes

:*Fixed a problem where output filters were not being saved
:*Improved performance when saving the component

;SmartMover Component
:Version: 1.0.1.2449

:;Changes

:*Fixed a backwards compatibility issue
:*Fixed a problem where output filters were not being saved

;Fuzzy Matching Component
:Version 2.0.0.2449

:;Changes

:*None

;MatchUp Component
:Version 2.2.0.2449

:;Changes

:*None

;Global Verify Component
:Version 2.0.0.2449

:;Changes

:*Added new Name Tab and Functionalities
:*Added new Phone Tab and Functionalities
:*Added new Email Tab and Functionalities

;IP Locator Component
:Version 1.0.0.2449

:;Changes

:*None

;Property Component
:Version 1.0.0.2449

:;Changes

:*New Component

==Build 4.3==
''Released August 2014''
;Contact Verification Component
:Version: 1.0.1. 2419
:Address Object Build: 2381
:Name Object Build: 2381
:Phone Object Build: 2381
:Email Object Build: 2381
:Geocoder Object Build: 2408
:MatchUp Object Build: 2408
:Database Date: 07/15/2014

:;Changes
:*Changed option "Peroform WS Lookup" for Email Check to default to false.
:*Fixed problem with Result Codes when switching from Community Edition to Full Version

;Personator Component
:Version: 1.0.0.2419

:;Changes
:*Fixed a problem where some options were disabled in certain conditions.
:*Pass-through data types now match exactly what is input.

;SmartMover Component
:Version: 1.0.1.2419

:;Changes
:*GUI modifications
:*Component now communicates with new v3 version of SmartMover web service.
:*Added Canadian Change of Address processing via Canadian SmartMover web service.

;Fuzzy Matching Component
:Version 2.0.0.2419

:;Changes
:*Added SSIS data type descriptions to ‘Options’ drop-down menu.

;MatchUp Component
:Version: 2.2.0.2419

:;Changes
:*Added SSIS data type descriptions to ‘Options’ drop-down menu.

;IPLocator Component
:Version: 2.2.0.2419

:;Changes
:*Initial Release

==Build 4.2==
''Released May 2014''

;Compatibility Summary
:The following DLLs are now being compiled in Visual Studio 2012:
:*Address Object
:*Name Object
:*Phone Object
:*Email Object
:*Geocoder Object
:*MatchUp Object

:This requires the installation of the 2012 Visual C++ Redistributable which is included in the SSIS Installation.

;Installer
:The Setup will automatically install 2012 Visual C++ Redistributable (x86 and x64) for compatibility with VS 2012 Compiled DLLs.

;Contact Verification Component
:Version: 1.0.1. 2368
:Address Object Build: 2362
:Name Object Build: 2362
:Phone Object Build: 2362
:Email Object Build: 2362
:Geocoder Object Build: 2362
:MatchUp Object Build: 2362
:Database Date: 04/15/2014

:;Changes

:*Added additional option in the configuration file for DisableAddressSwapping. This option can be set to true in order to permanently disable the swapping of AddressLine1 and AddressLine2.

;Personator Component
:Version: 1.0.0. 2368

:;Changes

:*Added ‘Freeform’ input address field option.
:*Set maximum output field size to 255 instead of 256 (particularly problematic for Excel).
:*Actions were sometimes unselected automatically.
:*Pass-through columns were not always passing through data.
:*Changed verification so that outputting just a result code is not an error.
:*Pass-through's ‘Select All’ button didn’t always work.
:*No default was selected for the Append options.

;MatchUp Component
:Version: 2.2.0. 2368

:;Changes

:*Fixed a problem with date-distance matchcodes; dates with trailing spaces weren’t properly parsed.
:*Fixed a problem with ‘Join with Spaces’ not properly working with an Intersection Lookup source.
:*Fixed a problem where editing survivorship output column size was not getting saved.
:*Survivorship mode ‘Average’ wasn’t working correctly for integers.

;Global Verify Component
:Version: 2.2.0. 2368

:;Changes

:*Added Delivery Lines Option in the GUI for outputting the complete Global Mailing address in AddressLines 1 - 8.

==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]]

Build History:SSIS:Data Quality Components

2016-01-04T23:45:37Z

Oscar: /* Build 5.4 */

[[SSIS:Data Quality Components|← SSIS:Data Quality Components]]
{{CustomTOC}}

==Build 5.4==
''Released November 2015''
:''Patch Released January 2016 [Build 2683]''

;Contact Verification Component
:Version: 1.0.1.2683
:Address Object Build: 2575
:Name Object Build: 2613
:Phone Object Build: 2613
:Email Object Build: 2554
:Geocoder Object Build: 2670
:MatchUp Object Build: 2628
:IpLocator Object Build: 2615
:Database Date: 10/15/2015

:;Changes

:*Community edition now requires a community edition license key, rather than no license key

;Personator Component
:Version: 1.0.0.2683

:;Changes

:*Fixed an issue with transaction size

;SmartMover Component
:Version: 1.0.1.2683

:;Changes

:*Transaction size setting locked to 100 records in accordance to USPS regulations

;Fuzzy Matching Component
:Version 2.0.0.2683

:;Changes

:*None

;MatchUp Component
:Version 2.2.0.2683

:;Changes

:*International Matchup capabilities now added to Matchup Component
:*Community edition now requires a community edition license key, rather than no license key\

;Global Verify Component
:Version 2.0.0.2683
:Global Address Object Build: 2620 (32bit), 2600 (64bit)
:;Changes

:*Added new On-Premise component
:*New processing modes: Webservice, On-Premise, Hybrid. WS sends all records to webservice, on-premise sends all records to the local object, and hybrid sends specified records to webservice OR the local object.

;IP Locator Component
:Version 1.0.0.2683

:;Changes

:*None

;Property Component
:Version 1.0.0.2683

:;Changes

:*None

;Profiler Component
:Version 1.0.0.2683

:;Changes

:*Community edition now requires a community edition license key, rather than no license key

==Build 5.3==
''Released August 2015''

;Contact Verification Component
:Version: 1.0.1.2626
:Address Object Build: 2613
:Name Object Build: 2613
:Phone Object Build: 2613
:Email Object Build: 2554
:Geocoder Object Build: 2615
:MatchUp Object Build: 2564
:IpLocator Object Build: 2554
:Database Date: 7/15/2015

:;Changes

:*Added more result codes to the output result filter

;Personator Component
:Version: 1.0.0.2626

:;Changes

:*Fixed a problem where the "Verify" action was not being sent
:*Fixed a problem where the Personator window would crash under certain circumstances
:*Added more result codes to the output result filter

;SmartMover Component
:Version: 1.0.1.2626

:;Changes

:*Files with less than 100 records will not be processed as per USPS regulations

;Fuzzy Matching Component
:Version 2.0.0.2626

:;Changes

:*Fixed spelling error in output tab

;MatchUp Component
:Version 2.2.0.2626

:;Changes

:*Fixed an issue where matchcodes could not use (UK) data types
:*Fixed an issue where DT_Numeric data types could not have a precision value greater than scale value
:*Fixed an issue where the advanced survivorship would crash the component in certain circumstances
:*Fixed several spelling mistakes

;Global Verify Component
:Version 2.0.0.2626
:Global Address Object Build: 2620 (32bit), 2600 (64bit)
:;Changes

:*Added new On-Premise component
:*With a proper license string, users can now verify global data on their machine rather than web service
:*Fixed various issues with On-Premise mode

;IP Locator Component
:Version 1.0.0.2626

:;Changes

:*None

;Property Component
:Version 1.0.0.2626

:;Changes

:*None

;Profiler Component
:Version 1.0.0.2626

:;Changes

:*None

==Build 5.2==
''Released May 2015''

;Contact Verification Component
:Version: 1.0.1.2575
:Address Object Build: 2554
:Name Object Build: 2554
:Phone Object Build: 2554
:Email Object Build: 2554
:Geocoder Object Build: 2554
:MatchUp Object Build: 2554
:IpLocator Object Build: 2554
:Database Date: 4/15/2015

:;Changes

:*fixed "Decimal" option unselectable in "Default Lat/Long Column Type"

;Personator Component
:Version: 1.0.0.2575

:;Changes

:*Personator restriction fixes and GUI changes.
:*Move confidence option now has "Loose" and "Strict" options.

;SmartMover Component
:Version: 1.0.1.2575

:;Changes

:*None

;Fuzzy Matching Component
:Version 2.0.0.2575

:;Changes

:*None

;MatchUp Component
:Version 2.2.0.2575

:;Changes

:*fixed MatchCode Editor swap crash

;Global Verify Component
:Version 2.0.0.2575

:;Changes

:*Fixed a few German translations and spelling
:*German localization for GV.
:*Global Email interface changes.
:*Output filter ES23 description update

;IP Locator Component
:Version 1.0.0.2575

:;Changes

:*None

;Property Component
:Version 1.0.0.2575

:;Changes

:*None

;Profiler Component
:Version 1.0.0.2575

:;Changes

:*Added InferredColumnType column.
:*Fixed issue where users would get error if they didn’t specify any output fields on the passthrough/results pin.

==Build 5.1==
''Released February 2015''

;Contact Verification Component
:Version: 1.0.1.2503
:Address Object Build: 2502
:Name Object Build: 2502
:Phone Object Build: 2502
:Email Object Build: 2502
:Geocoder Object Build: 2502
:MatchUp Object Build: 2408
:IpLocator Object Build: 2502
:Database Date: 1/15/2015

:;Changes

:*Fixed behavior of ‘Output Filter’ tab’s Filter controls in some instances.

;Personator Component
:Version: 1.0.0.2499

:;Changes

:*Added Demographics fields.

;SmartMover Component
:Version: 1.0.1.2503

:;Changes

:*None

;Fuzzy Matching Component
:Version 2.0.0.2502

:;Changes

:*None

;MatchUp Component
:Version 2.2.0.2499

:;Changes

:*Fixed issue where slow machines would crash if user changed tabs quickly during GUI startup.

;Global Verify Component
:Version 2.0.0.2503

:;Changes

:*Dialog not saving changes in rare instances.
:*User is now allowed to pass Advanced Configuration test with only some activated web services.
:*‘Default Lat/Long Column Type’ would not display checkmark if the selection was ‘Decimal’

;IP Locator Component
:Version 1.0.0.2503

:;Changes

:*None

;Property Component
:Version 1.0.0.2499

:;Changes

:*None

;Profiler Component
:Version 1.0.0.2503

:;Changes

:*Fixed issue where users would get error if they didn’t specify any output fields on the passthrough/results pin.

==Build 4.4==
''Released November 2014''
;Contact Verification Component
:Version: 1.0.1.2449
:Address Object Build: 2431
:Name Object Build: 2431
:Phone Object Build: 2431
:Email Object Build: 2431
:Geocoder Object Build: 2441
:MatchUp Object Build: 2441
:IpLocator Object Build: 2441
:Database Date: 10/15/2014

:;Changes

:*None

;Personator Component
:Version: 1.0.0.2449

:;Changes

:*Fixed a problem where output filters were not being saved
:*Improved performance when saving the component

;SmartMover Component
:Version: 1.0.1.2449

:;Changes

:*Fixed a backwards compatibility issue
:*Fixed a problem where output filters were not being saved

;Fuzzy Matching Component
:Version 2.0.0.2449

:;Changes

:*None

;MatchUp Component
:Version 2.2.0.2449

:;Changes

:*None

;Global Verify Component
:Version 2.0.0.2449

:;Changes

:*Added new Name Tab and Functionalities
:*Added new Phone Tab and Functionalities
:*Added new Email Tab and Functionalities

;IP Locator Component
:Version 1.0.0.2449

:;Changes

:*None

;Property Component
:Version 1.0.0.2449

:;Changes

:*New Component

==Build 4.3==
''Released August 2014''
;Contact Verification Component
:Version: 1.0.1. 2419
:Address Object Build: 2381
:Name Object Build: 2381
:Phone Object Build: 2381
:Email Object Build: 2381
:Geocoder Object Build: 2408
:MatchUp Object Build: 2408
:Database Date: 07/15/2014

:;Changes
:*Changed option "Peroform WS Lookup" for Email Check to default to false.
:*Fixed problem with Result Codes when switching from Community Edition to Full Version

;Personator Component
:Version: 1.0.0.2419

:;Changes
:*Fixed a problem where some options were disabled in certain conditions.
:*Pass-through data types now match exactly what is input.

;SmartMover Component
:Version: 1.0.1.2419

:;Changes
:*GUI modifications
:*Component now communicates with new v3 version of SmartMover web service.
:*Added Canadian Change of Address processing via Canadian SmartMover web service.

;Fuzzy Matching Component
:Version 2.0.0.2419

:;Changes
:*Added SSIS data type descriptions to ‘Options’ drop-down menu.

;MatchUp Component
:Version: 2.2.0.2419

:;Changes
:*Added SSIS data type descriptions to ‘Options’ drop-down menu.

;IPLocator Component
:Version: 2.2.0.2419

:;Changes
:*Initial Release

==Build 4.2==
''Released May 2014''

;Compatibility Summary
:The following DLLs are now being compiled in Visual Studio 2012:
:*Address Object
:*Name Object
:*Phone Object
:*Email Object
:*Geocoder Object
:*MatchUp Object

:This requires the installation of the 2012 Visual C++ Redistributable which is included in the SSIS Installation.

;Installer
:The Setup will automatically install 2012 Visual C++ Redistributable (x86 and x64) for compatibility with VS 2012 Compiled DLLs.

;Contact Verification Component
:Version: 1.0.1. 2368
:Address Object Build: 2362
:Name Object Build: 2362
:Phone Object Build: 2362
:Email Object Build: 2362
:Geocoder Object Build: 2362
:MatchUp Object Build: 2362
:Database Date: 04/15/2014

:;Changes

:*Added additional option in the configuration file for DisableAddressSwapping. This option can be set to true in order to permanently disable the swapping of AddressLine1 and AddressLine2.

;Personator Component
:Version: 1.0.0. 2368

:;Changes

:*Added ‘Freeform’ input address field option.
:*Set maximum output field size to 255 instead of 256 (particularly problematic for Excel).
:*Actions were sometimes unselected automatically.
:*Pass-through columns were not always passing through data.
:*Changed verification so that outputting just a result code is not an error.
:*Pass-through's ‘Select All’ button didn’t always work.
:*No default was selected for the Append options.

;MatchUp Component
:Version: 2.2.0. 2368

:;Changes

:*Fixed a problem with date-distance matchcodes; dates with trailing spaces weren’t properly parsed.
:*Fixed a problem with ‘Join with Spaces’ not properly working with an Intersection Lookup source.
:*Fixed a problem where editing survivorship output column size was not getting saved.
:*Survivorship mode ‘Average’ wasn’t working correctly for integers.

;Global Verify Component
:Version: 2.2.0. 2368

:;Changes

:*Added Delivery Lines Option in the GUI for outputting the complete Global Mailing address in AddressLines 1 - 8.

==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]]