When to use Decode instead of Lookup Transformation

Lookup transformation we use when we have a scenario where we need to lookup from various target and pass the value ,so instead of using all the lookup tables in the mapping what we can do is to include one lookup and fetdch the require value from all the tables and pass to the target.

The same logic can be also done using Decode statement.But in can only be done for small set of unchanging values.While using decode Informatica server doesnot have to lookup up seperate table,the values are brought into the expression itself whereas for lookup Informatica server needs to lookup table from database.

Dropping of Keys and Constraints in Informatica

When we load millions of records using informatica workflow with keys and constaraints on the Target table then it can cause slowdown of the job.In such cases we need to drop the constraints and keys and then load the data.Otherwise the worklfow will run slow.Once all the records are loaded you can rebuild it.

Also as a convinent solution its  better to create Informatica stored procedure for dropping aswell as rebuilding of the constraints.Before running the Informatica workflow the stored procedure can be run as Pre and Post of workflow job.

Transformation errors In Informatica Workflows

While running Informatica workflow we may get Transformation errors.When the number of transformation errors are more it affects the speed of Informatica server because the server needs to go back and find the reason for the error and reject those records.As we know the transformation error can be of any type either Informatica mapping datatype mismatch,expression invalidation etc.In order to find the type of error we can check the session log and then change the mapping accordingly.

In some cases where there are many transformation errors coming we can set a lower tracing level and run the workflow but this is not feasible in all cases and is not a good solution.

Below is an example of transformation

Scheduling Workflow in Informatica

Scheduling a workflow in Informatica is quite easy. Normally we run the workflow manually but when we need to run the workflow at periodic interval of time then we can use Informatica scheduler. Informatica Scheduler have various run options like:

1. Run on Integration Service Initialization

2. Run on Demand

3.Run Continuously.

Using the workflow setting we can run, schedule and remove the scheduler. The workflow runs purely based on what setting we give for the workflow. And once the settings are changed Integration service runs the workflow based on the new workflow settings.

If the scheduler for a workflow is removed then the workflow becomes invalid. Also the scheduler can be either reusable or non-reusable scheduler. If it’s reusable scheduler then the same scheduler can be used for other mappings too

Please share your valuable comments