Labeler

Decision

Standardizer

Parser

Number of Columns in the file

Number of Rows in the source data

Amount of memory and speed of the processor on the server

All of the above

TRUE

FALSE

By running the DQ Client installer

The Analyst defines the table in the Analyst tool, and the mappings in the Developer tool create and populate the appropriate tables

The Analyst populates and creates the table in the Analyst tool

The Administrator needs to create a DQA Service and associate it with the staging database

Only mappings using a Case Converter and a Standardizer can be used on data in Excel.

Only mappings using non active transformations can be used in DQ for Excel.

All DQ transformations, including Matching and Consolidation can be used in DQ for Excel.

All DQ and Core Transformations can be used in DQ for Excel, there is no limitation.

The same icon is used to indicate a shared and non shared project.

Comments that are added to a profile in the Analyst can be viewed by the Developer in the same profile in the Developer Tool.

Permissions need to be assigned to each Folder within the project so users of shared projects can access all the objects.

Rules that were created In the Analyst Tool will be visible In the Developer but Developer built rules can not be made available in the Analyst.

Performance

Scalability

Batch access

DQ as part of ETL process