Search results

Jump to navigation Jump to search
  • ==Matchup Component FAQ== ==Contact Verify Component FAQ==
    261 bytes (31 words) - 20:31, 13 January 2016
  • ...dialog is where you enter the basic information required for the Profiler Component to connect to the underlying Melissa Data libraries. ===Profiler Settings===
    2 KB (238 words) - 21:24, 19 December 2016
  • ==Matchup Component FAQ== ==Contact Verify Component FAQ==
    1 KB (132 words) - 17:08, 23 August 2017
  • The following steps will guide you in the basic usage of the Profiler Component. ==Add Component==
    1 KB (222 words) - 21:24, 11 January 2017
  • The following steps will guide you in the basic usage of Profiler for SSIS. In the Profiler Component, navigate to File > Advanced Configuration.
    2 KB (249 words) - 00:32, 14 November 2015
  • The following steps will guide you in the basic usage of Profiler for Pentaho. ==Add Component==
    1 KB (219 words) - 18:54, 19 October 2015
  • Specify an output file that the profiler will use to store its results. If you don't specify a path, a temporary fil ==[[Pentaho/Contact Zone:Profiler:Output Pins|Output Pins]]==
    1 KB (167 words) - 21:38, 11 January 2017
  • Specify an output file that the profiler will use to store its results. If you don't specify a path, a temporary fil ==[[Pentaho:Profiler:Output Pins|Output Pins]]==
    1 KB (160 words) - 15:54, 19 October 2015
  • [[SSIS:Profiler|← SSIS:Profiler]] ;What kinds of speeds/throughput can the Profiler component do?
    2 KB (223 words) - 23:39, 23 August 2017
  • To configure the Contact Verify Component for On-Premise processing, just select a data path: ...and its data files. The default path should work unless you installed the component to a different folder.
    2 KB (345 words) - 21:25, 11 January 2017
  • To configure the Contact Verify Component for On-Premise processing, just select a data path: ...and its data files. The default path should work unless you installed the component to a different folder.
    2 KB (342 words) - 22:05, 19 December 2016
  • ...Global Verify, IP Locator, MatchUp, Personator, Property, SmartMover, and Profiler components. These components offer an array of useful data cleansing option ==Component List==
    3 KB (458 words) - 23:31, 30 December 2016
  • ==Profiler Overview== Melissa Data’s Data Profiler is a component that can be used to analyze a table’s data. This analysis provides a larg
    2 KB (342 words) - 23:39, 23 August 2017
  • ==Profiler Overview== Melissa Data’s Data Profiler is a component that can be used to analyze a table’s data. This analysis provides a larg
    2 KB (331 words) - 21:17, 11 January 2017
  • ==Business Coder Component== ==Cleanser Component==
    3 KB (409 words) - 23:46, 17 January 2017
  • ==Profiler Overview== Melissa Data’s Data Profiler is a component that can be used to analyze a table’s data. This analysis provides a larg
    2 KB (328 words) - 18:47, 15 September 2015
  • ...unlocks the full functionality of the component. Without the License Key, Profiler Object will only function in demo mode. ...ey using an environment variable called MD_LICENSE. If you want to try out Profiler Object, see the section below about [[#Demo Mode|Demo Mode]].
    2 KB (288 words) - 21:16, 19 December 2016
  • *[[Pentaho/Contact Zone:Basics|Component Overview]] *[[Pentaho/Contact Zone:Profiler|Profiler]]
    2 KB (251 words) - 22:18, 10 June 2021
  • !Component |Profiler
    3 KB (468 words) - 01:48, 7 January 2023
  • *[[Pentaho/Contact Zone:Basics|Component Overview]] *[[Pentaho/Contact Zone:Profiler|Profiler]]
    3 KB (349 words) - 23:57, 20 April 2022
  • [[Profiler Object:Reference|← Profiler Object Reference]] ...the paths to the necessary data files, the License Key, and initialize the Profiler Interface:
    13 KB (1,527 words) - 21:18, 19 December 2016
  • <!--*[[SSIS:Advisory|Global Verify Component - Global Email Update Advisory]]--> *[[FAQ:SSIS:Component Specific|Component Specific FAQ & Optimizations]]
    4 KB (470 words) - 18:07, 15 June 2023
  • ...uite Components have a Community Edition. This is a no-cost version of the component available to you for trying out the components. !Component
    3 KB (396 words) - 15:26, 6 September 2018
  • In MatchUp, clustering is made possible when we have at least one component common to all used matchcode combinations. Since ZIP5 is used in all matchc ...lustering issues. You can check this by using one of our [[Profiler Object|Profiler products]] to check for NULL/Empty values, as well incorrect data types in
    2 KB (360 words) - 14:44, 2 October 2018
  • ...the Data Matching area, and specifically the Melissa Data flagship MatchUp component, which organizes data records into identifiable duplicate groups and links ...sources meet the organization’s quality standards. Some of the features of Profiler include Column Profiling – This task identifies problems in your data, su
    4 KB (515 words) - 21:04, 21 May 2015
  • *Copy of Component DLLS: *Component Pipeline Dlls:
    10 KB (1,551 words) - 22:27, 20 August 2020
  • [[Category:Profiler Component]]
    2 KB (314 words) - 21:37, 11 January 2017
  • :*Profiler ;New Personator Component
    8 KB (1,085 words) - 21:14, 27 October 2017
  • ...remise components to increase speed, utilizing a Balanced Data Distributor component to send data to each instance. !SSIS Component!!Throughput (records / hour)
    4 KB (497 words) - 00:00, 25 March 2022
  • [[Category:Profiler Component]]
    3 KB (393 words) - 21:34, 11 January 2017
  • ...the Data Matching area, and specifically the Melissa Data flagship MatchUp component, which organizes data records into identifiable duplicate groups and links ...sources meet the organization’s quality standards. Some of the features of Profiler include Column Profiling – This task identifies problems in your data, su
    5 KB (764 words) - 00:33, 3 January 2017
  • Unlike the other Melissa Data components, the Profiler Component has a set of 11 possible output pins. Each output pin will contain a static The following are the possible output pins for the Profiler Component:
    25 KB (3,665 words) - 21:30, 11 January 2017
  • Unlike the other Melissa Data components for Pentaho, the Profiler Component has a set of 11 possible output pins. Each output pin will contain a static The following are the possible output pins for the Profiler Component:
    25 KB (3,662 words) - 15:57, 19 October 2015
  • Unlike the other Melissa Data components for SSIS, the Profiler Component has a set of 11 possible output pins. Each output pin will contain a static The following are the possible output pins for the Profiler Component:
    25 KB (3,665 words) - 20:11, 22 August 2016
  • |[[Returned Result Codes:APIs#Profiler Object|Profiler Object]] '''Contact Verify Component'''
    39 KB (5,907 words) - 22:40, 3 June 2019
  • |Image=[[Image:ICON_API_ProfilerObject.png|84px|Profiler Object|link=#Profiler Object]] |Link=[[#Profiler Object|Profiler Object]]
    128 KB (19,482 words) - 23:27, 19 February 2024
  • |Component Mismatch Error |Component Error
    90 KB (14,655 words) - 23:27, 19 February 2024