What is Transaction Control Transformation?
Exchange Control is a functioning and associated change which permits us to commit or roll back exchanges during the execution of the planning. Commit and rollback tasks are vital as it ensures the accessibility of information.
While handling a high volume of information, there can be a circumstance when committing the information to the objective. On the off chance that a carry-out is performed too habitually, it will be an above to the framework. In the event that a commit is performed past the point of no return, on account of disappointment, there are chances of information misfortune.
So to give adaptability Transaction control change is given.
TCL COMMIT and ROLLBACK Commands
There are five in-fabricated factors accessible in this change to deal with the activity.
Model:
In this model, we will commit information to the objective when dept no =20 conditions is seen as evident
Stage 1 - Create a plan with EMP as source and EMP_TARGET as target
Exchange Control Transformation in Informatica with EXAMPLE
Stage 2 - Create another change utilizing the change menu, then, at that point,
Select an exchange control as the new change
Enter change name "tc_commit_dept20"
Select make choice
Exchange Control Transformation in Informatica with EXAMPLE
Stage 3 - The exchange control change will be made, select done fasten
The Transaction Control Transformation is used to define
transaction boundaries within a mapping. It helps maintain data consistency and
integrity by controlling when data changes are committed or rolled back in the
target system. This is particularly important in scenarios where multiple data
operations need to be treated as a single transaction.
2. Types of Transaction Control Transformation
In Informatica, there are two main types of Transaction
Control Transformations:
3. Configuring Transaction Control Transformation
Configuring the Transaction Control Transformation involves
defining when and under what conditions commits or rollbacks should occur. This
typically involves setting parameters such as:
4. Use Cases for Transaction Control Transformation
Transaction Control Transformations are commonly used in ETL
processes for scenarios such as:
5. Best Practices for Transaction Control Transformation
To use Transaction Control Transformations effectively,
consider the following best practices:
Exchange Control Transformation in Informatica with EXAMPLE
Stage 4 - Drag and drop every one of the segments from the source qualifier to the exchange control change then, at that point, connect every one of the sections from the exchange control change to the objective table
Exchange Control Transformation in Informatica with EXAMPLE
Stage 5 - Double snap on the exchange control change and afterward in the alter property window
Select property tab
Click on the exchange control manager symbol
Exchange Control Transformation in Informatica with EXAMPLE
Stage 6 - in the articulation supervisor enter the articulation -
"iif(deptno=20,tc_commit_before,tc_continue_transaction)" and select OK
It implies on the off chance that deptno 20 is found, commit exchange in target, else the ongoing system.
Exchange Control Transformation in Informatica with EXAMPLE
Stage 7 - Select OK in the past window
Exchange Control Transformation in Informatica with EXAMPLE
Presently save the planning and execute it subsequent to making meetings and work processes. This planning will commit the information to the objective at whatever point office number 20 is tracked down in the information.
Joiner transformation in Informatica |
Router Transformation in Informatica |
Mappings in Informatica |
Workflow Monitor in Informatica |