How to Avoid The Usage of SQL Overrides in Informatica PowerCenter Mappings

How to Avoid The Usage of SQL Overrides in Informatica PowerCenter Mappings

Many Informatica PowerCenter developers tend to use SQL Override during mapping development. Developers finds it easy and more productive to use SQL Override. At the same time ETL Architects do not like SQL Overrides as it hide the ETL logic from metadata manager. In this article lets see the options available to avoid SQL Override in different transformations.

Continue Reading

Data Security Using Informatica PowerCenter Data Masking Transformation

Data Security Using Informatica PowerCenter Data Masking Transformation

You might have come across scenario where in you do not have enough good data in your Development and QA regions for your testing purpose; and you are not allowed to copy over data from production environment due to the data security reasons. Now using Informatica PowerCenter data masking transformation you can overcome such scenarios. In this article, lets see the usage of masking transformation.

Continue Reading

Transaction Control Transformation to Control Commit and Rollback in Your ETL

Transaction Control Transformation to Control Commit and Rollback in Your ETL

In a typical Informatica PowerCenter workflow data is committed to the target table after a predefined number of rows are processed into target, which is specified in the session properties. But there are scenarios in which you need more control on the commits and rollbacks.  In this article, lets see how we can achieve this using Transaction Control Transformation.

Continue Reading

Informatica PowerCenter Design Best Practices and Guidelines

Informatica PowerCenter Design Best Practices and Guidelines

A high-level systematic ETL design will help to build efficient and flexible ETL processes. So special care should be given in the design phase of your project. In following we will be covering the key points one should keep in mind while designing an ETL process. The following recommendations can be integrated into your ETL design and development processes to simplify the effort and improve the overall quality of the finished product.

Continue Reading

Design Approach to Handle Late Arriving Dimensions and Late Arriving Facts

Design Approach to Handle Late Arriving Dimensions and Late Arriving Facts

In the typical case for a data warehouse, dimensions are processed first and the facts are loaded later, with the assumption that all required dimension data is already in place. This may not be true in all cases because of nature of your business process or the source application behavior. Fact data also, can be sent from the source application to the warehouse way later than the actual fact data is created. In this article lets discusses several options for handling late arriving dimension and Facts.

Continue Reading