Active Transformation An active transformation changes the number of rows that p

ass through the mapping.

1. Filter Transformation --> To filter data as pe
r given condition, for eg, Salary < 2000
2. Router Transformation --> Router vs Filter, ro
uter has default group which contains discarded data.
3. Union Transformation --> To combine data from
multiple input source, but has only 1 output.
--> It works similar to UNION ALL, doesnt remove duplicate data and all inpu
ts and output must have same port, datatype and scale.
--> For removing duplicate we have to use either Filter or Router transofrmation
s seperately.
--> We cannot use a Sequence Generator or Update Strategy transformation upstrea
m from a Union transformation.
4. Sorter Transformations --> Used to sort data ei
ther in ascending or descending based on sort key we specified, we can specify m
ore than
one port as sort key.
--> We can specify whether sort must be case sensitive, upper case will be sorte
d above lower case.
--> We must specify the sort cache size, must be less than the powercenter ram,
if space not enough session will fail.
--> We can specify DISTINCT duplicate will be ignored, and sorting will be on al
l ports.
5. Rank Transformation --> To rank data and sel
ect top \bottom values based on rank.
--> It will have a RANKIDEX
--> We can get ranking of groups as well, using group option.
6. Aggregator Transformations --> The Aggregator transformatio
n allows us to perform aggregate calculations, such as averages and sums.
--> The transformation language includes the following aggregate functions:
AVG, COUNT , MAX, MIN, SUM
FIRST, LAST
MEDIAN, PERCENTILE, STDDEV, VARIANCE
7. Joiner Transformation --> This is to join two
data inputs just like SQL join, we have MASTER and DETAIL,
always input with less rows must be DETAIL.
Types of Joins:
 Normal
Master Outer
Detail Outer
Full Outer
--> Only Equal operation allowed.
8. Source Qualifier Transformation --> The Source Qualifier
transformation represents the rows that the PowerCenter Server reads when it ru
ns a session.
--> We can join multiple data inputs to represent One source qualifier.
--> We can filter rows, PC server uses where clause.
--> We can use DISTINCT, to eliminate duplicate.
--> We can selected sorted ports to sort the data, PC server uses order by claus
e in SQL.
--> We can specify OUTER JOIN instead of the default equi join of PC server.
--> Can create custom query also specify PRE_SQL & POST_SQL.
9. Update Strategy Transformation --> if we want to update
, delete or reject rows coming from source based on some condition.
--> Update Strategy is used with Lookup Transformation. In DWH, we create a Look
up on target table
to determine whether a row already exists or not. Then we insert, update, delete
or reject the source record as per business need.
10. Normalizer Transformation --> The Normalizer trans
formation normalizes records from COBOL and relational sources, allowing us to
organize the data.
--> Use a Normalizer transformation instead of the Source Qualifier transformati
on when we normalize a COBOL source.
-->We can also use the Normalizer transformation with relational sources to creat
e multiple rows from a
Single row of data.
--> To Convert coloumns into rows we use Normalizer.
Advanced External Procedure Transformation

Passive Transformation Passive transformations do not change the number of rows

that pass through the mapping.
1. Expression Transformation --> Performance expressi
on operation on single row, like add, subtract , multily, concat, etc.
(3 ports INPUT, OUTPUT, VARIABLE)
 2. Sequence Generator Transformation--> The Sequence Generator t
ransformation generates numeric values.
--> Use the Sequence Generator to create unique primary key values, replace miss
ing primary keys
or cycle through a sequential range of numbers.
--> Use the CURRVAL & NEXTVAL port to generate sequence numbers by connecting it
to a transformation or target.
3. Lookup Transformation --> It looks for
the data in the source as per the given condition.
--> Source can be relational tables or Flat files.
4. Stored Procedure Transformation --> To execute DB stored
Procedure.
5. XML Source Qualifier T\F -->This is to imp
ort XML sources and use it in our mapping.
--> In case of XML sources, XML Qualifier is used by default.
6. External Procedure Transformation
MAPPLETS:
--> A mapplet is a reusable object that we create in the Mapplet Designer.

It contains a set of transformations and lets us reuse that transformation logic

in multiple mappings.

Created in Mapplet Designer in Designer Tool.

7. Input Transformation(Mapplet) --> Mapplet input can or
iginate from a source definition and/or from an Input transformation in the mapp
let.
We can create multiple pipelines in a mapplet.

--> We use Mapplet Input transformation to give input to mapplet.

--> Use of Mapplet Input transformation is optional.
8. Output Transformation(Mapplet) --> The output of a mapp
let is not connected to any target table.

--> We must use Mapplet Output transformation to store mapplet output.

--> A mapplet must contain at least one Output transformation with at least one
connected port in the mapplet.

TASKS:
------