Why is BTET transaction processing overhead in Teradata?

Question

I have a requirement to call Teradata BTET from Informatica . can any one tell me that if I create a flow ( in one single mapping ) with a ---

--dummy talble as source and target and write into its pre-sql:

begin transaction;

lock A for write;

--after this I create a my flow of mapping where I will insert data in A table

--then in last I have a flow with same dummy table whose post-sql has command

end transaction;

will this work?

Answer 1

• BTET makes all the queries running between BT and ET as single transaction . If any of query fails then the entire set of queries will not be committed.

• BTET also has an overhead with locking , since it holds locks on tables till the ET is occured or all the queries have executed successfully

• DDL statements cannot be used everywhere in BTET processing , but these statements can be given towards the end of BTET transaction.

• Using large number of BTET caused transient Journal to grow and has tendancy for System Restarts