What are the type of repositories created using Informatica Repository Manager?
Informatica PowerCenter includes following type of repositories:
Standalone Repository, which functions individually.
Global Repository which is a centralized repository in a domain and it also contain shared objects across the repositories in a domain.
Local Repository is one which is within a domain.
Versioned Repository can be either local or global but it allows version control.
What is a code page?
A code page contains encoding to specify characters in a set of one or more languages and is selected based on source of the data. The set code page refers to a specific set of data that describes the characters the application recognizes. This influences the way that application stores, receives, and sends character data.
What do you mean by code page compatibility?
When two code pages are compatible, the characters encoded in the two code pages are virtually identical which ensures no data loss. This compatibility is used for accurate data movement when the Informatica Sever runs in the Unicode data movement mode. One code page can be a subset or superset of another. For proper data movement, the target code page must be a superset of the source code page.
What is a transformation?
A transformation is a repository object that generates, modifies, or passes data. The Designer provides a set of transformations that perform specific functions. Each transformation has rules for configuring and connecting in a mapping. Transformation is created to use once in a mapping or reusable transformations can be created to use in multiple mappings.
Eg. Aggregator transformation performs calculations on groups of data.
What are the types of loading in Informatica?
There are two types of loading in informatica, normal loading and bulk loading.
In normal loading record by record are loaded and writes log for that. In this longer time is needed to load data to the target.
In bulk loading number of records are loaded at a time to target database. It takes less time to load data to the target than in normal loading.
Why do we use the lookup transformation? How can we improve session performance in aggregator transformation?
A lookup transformation is used for checking the matched values from the source or target tables and check whether the record already existing in the table. It is also used for updating the slowly changing dimensions and also performs some calculations.
Using Incremental Aggregation we create Sorted Input option to improve the performance since performance is reduced using the caches.
What is the difference between static cache and dynamic cache?
In case of dynamic cache, when we are inserting a new row it checks the lookup cache to see if it exists, if not inserts it into the target as well as the cache but in case of static cache the new row is written only in the target and not the lookup cache.
The lookup cache remains static and does not change during the session but incase of dynamic cache the server inserts, updates in the cache during session.