Features and Enhancements of

Informatica Power center 7.1 and 7.0

TCS Internal
 Power Center Server
 Power centre server processing enhancements. So server reads a block of rows at a
time. This improves processing performance for most sessions.

 Server supports CLOB/BLOB Data types.

 It supports the function SOUNDEX(7.0)

Eg:-Select ename from emp where soundex(ename)=soundex(‘SMITH’);

We can use Teradata warehouse builder to load to Teradata. Teradata warehouse
builder can simultaneously read from multiple sources and load data in to one or more
tables.

Repository Server
Export and import objects using the Repository Manager and pmrep(7.0)

Exchange metadata with Business Intelligence tools. Export metadata to and import
metadata from other business intelligence tools such as Cognos Report Net and
Business Objects.

Compare objects in an XML file to the objects in the Repository when you import
objects.
TCS Internal
 Transformations
 Lookup Transformation supports look up as flat file (Flat file Lookup).
You can also use a lookup file parameter if you want the change the name
and location of a flat file between session runs.
 Union Transformation. It is used to merge multiple sources in to single
pipeline. It is similar to the UNION ALL SQL Statement (7.0)
 Custom Transformation API enhancements. It includes new-array
based functions that allow you to create procedure code that receives and
outputs a block of rows at a time
 Joiner transformation can be used to join two data streams that originate
from the same data source.

Usability
 Viewing active folders. Designer and Workflow Manager highlight the
active folder in the navigator.
 Copying Objects. You can now copy objects from all the power center
client tools using the copy wizard.(7.0)
 Compare Objects like workflows and tasks from the workflow manager
and also compare all objects with in the Repository Manager(7.0)

TCS Internal
  Validate the multiple objects (Mappings, mapplets, sessions,
workflows, worklets ) in the repository with out fetching them in to
the workspace.(7.0)
 * Refresh the session mappings . In workflow manager we can
refresh a session mapping.(7.0)

Workflow Monitor

 Open the multiple instances of Workflow Monitor on one machine

 Filtering the tasks by start and end time
 It displays workflow runs in Task View chronologically with the
most recent run at the top , displays the folders alphabetically.
 Remove the Navigator and Output window is possible.

TCS Internal
 Union Transformation
 It is a multiple input group transformation that you can use to merge data
from multiple pipelines or pipeline branches into one pipeline.
 Union transformation is used to merge data from multiple sources (it is
similar to using UNION ALL SQL statement)
 We can connect heterogeneous sources to a Union transformation.
 Union Transformation merges sources with matching ports and outputs the
data from one output group with the same ports as the input group.

Union Transformation Rules and Guidelines

 We can create a multiple input groups but only one output group.
 All input, output groups must have matching ports. The
precision,datatype, and scale must be identical across all groups.
 It doesn’t remove duplicate rows.
 You can not use a Sequence Generator or Update Strategy transformation
upstream from a Union transformations.

TCS Internal
 Components of the union transformation are Transformation tab, Properties
tab, Groups tab, Groups Ports tab.

Working with Groups and Ports

 Union Transformation has multiple input groups and one output group.
 We can create one or more input groups on the Groups tab. Designer creates
one output groups by default, can not edit or delete the output group.
 Ports of the Groups are added in Group Port tab.

TCS Internal
TCS Internal
 • Test Load
 With a test load option the Informatica Server reads and transforms
data without writing to targets.
 The Informatica Server generates all session files, and performs all
pre- and post-session functions, as if running the full session.
 The Informatica Server writes data to relational targets, but rolls
back the data when the session completes.
 other target types, such as flat file and SAP BW, the Informatica
Server does not write data to the targets.
Number of Rows to Test (Optional)
 Enter the number of source rows you want to test in the Number of
Rows to Test field .
 You cannot perform a test load on sessions using XML sources.
 You cannot perform a test load for Bulk mode.

TCS Internal
Steps to Create an Email Task
• In the Task Developer, choose Tasks-Create
• Select an Email task and enter a name for the task. Click Create.
• Click Done.
• Double-click the Email task in the workspace. The Edit Tasks dialog
box appears.

TCS Internal
TCS Internal
 • %a<> Attach the named file. The file must be local to
the Informatica Server

• %b -Session start time

• %c - Session completion time

• %d - Name of the repository containing the session

• %e - Session status

• %g - Attach the session log to the message

• %i - Session elapsed time (session completion

time-session start time)

TCS Internal
 • %l - Total records loaded

• %m - Name and version of the mapping used in the

session.

• %n - Name of the folder containing the session.

• %r - Total records rejected

• %s - Session name

• %t - Target table details, including read throughput

in bytes per second and write throughput in rows
per second.

TCS Internal
To configure suspension email:
In the Workflow Designer, open the workflow.
 Choose Workflows-Edit to open the workflow properties.
 On the General tab, select Suspension email.
 Click the Browse Emails button to select a reusable Email
task.
Note: The Workflow Manager returns an error message if you do
not have any reusable Email tasks in the folder. Create a reusable
Email task in the folder before you configure suspension email.

 Choose a reusable Email task and click OK.

TCS Internal
Working with Suspension Email
 This is used to configure a workflow to send email when the
Informatica Server suspends the workflow.
 when a task fails, the Informatica Server suspends the workflow and
sends the suspension email.

TCS Internal
General rules for writing efficient
SQL

TCS Internal
  Never do a calculation on an indexed column (e.g.,
WHERE salary*5 > :myvalue).

 Whenever possible, use the UNION statement instead of

OR conditions.

 Avoid the use of NOT IN or HAVING in the WHERE

clause. Instead, use the NOT EXISTS clause.

 Always specify numeric values in numeric form and

character values in character form (e.g., WHERE
emp_number = 565, WHERE emp_name = ‘Jones’).

 Avoid specifying NULL in an indexed column.

TCS Internal
 Use DECODE to reduce processing.

The DECODE statement provides a way to avoid having to scan the

same rows repetitively or to join the same table repetitively.

SELECT COUNT (*), SUM (salary)

FROM EMP
WHERE dept_no = 0020
AND emp_name LIKE ‘SMITH%’;
SELECT COUNT(*), SUM(salary)
FROM emp
WHERE dept_no = 0030
AND emp_name like ‘SMITH%’ ;

The same result can be achieve much more efficiently with DECODE:

SELECT COUNT(DECODE(dept_no, 0020, ‘X’, NULL)) D0020_kount,

COUNT(DECODE(dept_no, 0030, ‘X’, NULL)) D0030_kount,
SUM (DECODE(dept_no, 0020, salary, NULL)) D0020_sal,
SUM (DECODE(dept_no, 0030, salary, NULL)) D0030_sal
FROM emp WHERE emp_name LIKE ‘SMITH%’ ;
TCS Internal
  Always use table aliases when referencing columns.
 SELECT count (*) from EMP” may not be as fast as “SELECT
count (rowid) from emp”.
 Use NVL when using aggregate functions .
Eg: SELECT MAX (NVL (a.line_item_nbr, 0))
FROM submittal_transaction a
WHERE a.submittal_transaction_id = v_submittal_transaction_id;
1. In case more than one column is used in the aggregate function, NVL
has to be used for each column separately.
2. Eg: SELECT SUM (NVL (a.submittal_amount, 0) + NVL
(a.approved_amount,0)) FROM credit_submittal a;
 Avoid using unnecessary brackets. Do not place brackets around
the where clause unless necessary. Unnecessary brackets
increase parsing time and adversely affect query performance .

TCS Internal
 While using LIKE operator, if you are not using wildcards, then don’t
use LIKE. Use equality operator instead.
Eg. desig Like ‘DBA’ – Not optimized
desig=’DBA ’ – Optimized
desig like ‘DB%’ – Correct. But if you know the full string, better
to use it.
 When the number of condition in IN operator is less, use OR and =
operator .
Eg. WHERE dno IN (10,20,30) – Not optimized
Dno =10 OR dno = 20 OR dno=30 – Optimized.

 When you use ANY or ALL or BETWEEN operators, the query

optimizer expands the condition .So, it’s better that you expand the
condition as far as possible using OR operator.

Eg.1 Where Sal=ANY (5000, 6000) – Not optimized

Where sal=5000 OR sal = 6000 – Optimized

Eg2. Where sal >ALL (5000, 6000) – Not optimized

Where sal >5000 AND sal>6000 – Optimized

Eg3. Where sal BETWEEN 2000 AND 5000 – Not optimized

TCS Internal
Where sal >=2000 AND sal<=5000 – Optimized
 Try to avoid using the NOT logical operator as far as
possible. Use <> or! = Or ^= relational operators instead.
• Eg. NOT dno = (SELECT dno FROM emp WHERE
ename = TAYLOR')
– Not optimized
• deptno <> (SELECT deptno FROM emp WHERE
ename = 'TAYLOR') –
-- Optimized
 Try to avoid IN/NOT IN and use EXISTS/NOT EXISTS
• SELECT dname, dno FROM dept
WHERE dno NOT IN (SELECT dno from emp);
Not
Optimized
SELECT dname,dno FROM dept
WHERE dno NOT EXISTS (SELECT dno FROM
emp WHERE dept.dno= emp.dno); - Optimized
(Make sure the dno on emp is Indexed.)
TCS Internal
 Thank You
TCS Internal