Mapping Design Basics:- 45%

Mapping Design Advanced:- 20%

Others:- 35%
Admin Guide
Chapter 1: Understanding Domains --- Imp
Chapter 2: Managing Your Account --- Just read through
Chapter 3: Using Informatica Administrator --- Just read through
Chapter 4: Domain Management --- Imp
Chapter 7: Users and Groups --- Just read through
Chapter 8: Privileges and Roles --- Just read through
Chapter 10: High Availability --- Imp
Chapter 13: Data Integration Service --- Just read through
Chapter 15: PowerCenter Integration Service --- Imp
Chapter 16: PowerCenter Integration Service Architecture --- Imp
Chapter 18: PowerCenter Repository Service --- Just read through
Chapter 27: Managing the Grid --- Just read through
Chapter 28: Load Balancer --- Imp

Designer Guide
All chapters except the last 3 (13,14 and 15)

Workflow Basics Guide

All chapters

Workflow Advanced
All chapters except 13, 17, 18, 19, 20, 22, 23, 24

Transformations
Make sure to cover all Transformations given in the Syllabus.

Transformation Language
All chapters except 7 and 8. Make sure to pay attention to the details of functions.

Performance Tuning
All chapters. Simplest one.

SQL OVERRIDES -
Lookup Query
The Integration Service queries the lookup based on the ports and properties you configure in the Lookup
transformation. The Integration Service runs a default lookup query when the first row enters the Lookup
transformation.

If you use a lookup against a relational table, you can override the lookup query. You can use the override to
change the ORDER BY clause, add a WHERE clause, or transform the lookup data before it is cached.

If you configure a SQL override and a filter on the lookup query, the Integration Service ignores the filter.

Default Lookup Query

The default lookup query contains the following statements:
SELECT
The SELECT statement includes all the lookup ports in the mapping. To view the SELECT statement for
the lookup query, select the Use Custom Query property.
ORDER BY

The ORDER BY clause orders the columns in the same order they appear in the Lookup transformation.
The Integration Service generates the ORDER BY clause. You cannot view this when you generate the
default SQL.

SQL Override for a Lookup Query

 You can override the lookup query for a relational lookup. You can change the ORDER BY clause, add a
WHERE clause, and transform the lookup data before it is cached.

You can use reserved words and forward slashes in table names and column names.

You can enter a query to override the default lookup query completely. Or, you view and edit the default
lookup query. The default lookup query includes the lookup ports, output ports, and the return port.

SQL Override for an Uncached Lookup

You can define an SQL override for uncached lookups. You can override all of the SQL query including the
WHERE clause and ORDER BY clause.

The Developer tool generates a SELECT statement that includes the lookup ports, input/output ports, and the
WHERE clause based on the lookup condition. If the Lookup transformation is an unconnected lookup, the
SELECT statement includes the lookup ports and the return port.

Each column in the SELECT query uses an alias to define the output column. Do not change the syntax of
the column aliases in the SQL statement. If you change the syntax, the query fails. To reference input ports in
the WHERE clause, configure parameter binding. The following example includes a WHERE statement that
references the Name port:
SELECT EMPLOYEE.NAME as NAME, max(EMPLOYEE.ID) as ID from EMPLOYEE WHERE EMPLOYEE.NAME=?
NAME1?
You can use SQL functions in the SQL override. If you add a function to the SQL statement, the return
datatype must match the datatype of the column. For example, the datatype of ID matches the return type of
the MAX function:
SELECT EMPLOYEE.NAME as NAME, MAX(EMPLOYEE.ID) as ID FROM EMPLOYEE
Note: You cannot use subqueries in the SQL override for uncached lookups.

Reserved Words
If any lookup name or column name contains a database reserved word, such as MONTH or YEAR, the
mapping fails with database errors when the Integration Service executes SQL against the database.

You can create and maintain a reserved words file, reswords.txt, in the Integration Service installation directory. When
the Integration Service initializes a mapping, it searches the reswords.txt file and places quotes around reserved
words, and then executes the SQL against source, target, and lookup databases.

You might need to enable some databases, such as Microsoft SQL Server and Sybase, to use SQL-92 standards
regarding quoted identifiers. Use environment SQL to issue the command. For example, with Microsoft SQL Server,
use the following command:
SET QUOTED_IDENTIFIER ON

Guidelines for Overriding the Lookup Query

Certain rules and guidelines apply when you override a lookup query.

Consider the following guidelines when you override the lookup SQL query:

You can override the lookup SQL query for relational lookups.
Add a source lookup filter to filter the rows that are added to the lookup cache. This ensures that the
Integration Service inserts rows in the dynamic cache and target table that match the WHERE clause.
If multiple Lookup transformations share a lookup cache, use the same lookup SQL override for each
Lookup transformation.
 If a table name or column name in the lookup query contains a reserved word, enclose the reserved word
in quotes.
To override the lookup query for an uncached lookup, choose to return any value when the Integration
Service finds multiple matches.
You cannot add or delete any columns from the default SQL statement.
The SQL override cannot contain parameters or variables.

Overriding the Lookup Query

You can override the default lookup SQL query to create a customized query on the lookup source.
1. On the Properties view, select the Query tab.
2. Select Advanced.
3. Select Use Custom Query.
4. Edit the lookup query in the SQL Query area.
You can double-click a table name or column name to add it to the query.
5. Click Validate Query to validate the lookup query.
6. Select Push Custom Query to Database to run the lookup query in the database.

SQL Override and Dynamic Lookup Cache

Rules and Guidelines for Dynamic Lookup Caches
When you use a lookup SQL override, map the correct columns to the appropriate targets for lookup.

When you add a WHERE clause to the lookup SQL override, use a Filter transformation before the
Lookup transformation. This ensures that the Integration Service inserts rows in the dynamic cache and
target table that match the WHERE clause.