Profiling and Discovery Sizing Guidelines

Back Next

Overview

When you run a profile or scorecard in the Analyst tool or Developer tool, the application sends the request to the Data Integration Service. The Profiling Service Module converts the profile into one or more mappings. The Profiling Service Module sends the mappings to the LDTM for optimization and compilation. The LDTM passes the compiled mappings to DTM instances that get the profiling rules and run the profile or generate a scorecard for the profile.

The Profiling Service Module interacts with the following components:

Components	Description
Profiling Warehouse	The database that contains the profiling results. It can also contain cached source data for drilldown.
Relational Database Sources	Databases that contain data organized for efficient data processing. Modern relational databases are optimized to process the data that is stored in them, and the Profiling Service Module takes advantage of this optimization.
Flat File Sources	Files that contain data in delimited or fixed-width form.
Non-relational Sources	Non-relational sources of data organized for efficient data processing. The main type of non-relational database source is the mainframe, for example, an IMS or a VSAM database system. Another type of non-relational source is a SAP database. The Profiling Service Module requires additional resources to read a non-relational database source. For mainframe sources, the Profiling Service Module takes up most of the processing tasks to minimize the data access costs.

Rename Saved Search

Table of Contents

Profiling and Discovery Sizing Guidelines

Profiling and Discovery Sizing Guidelines

Overview

Overview