question

As @Usman Butt wrote, the **`TransactionOption`** needs to be set to **`Required`**. But it can be set even for a single data flow and do not needs to be set on a Sequence Container. Sequence container simplifies this if you want to set it for multiple control flow tasks (including data flow) as the default TransactionOption` is **`Supported`**, what means if the parent has `TransactionOption` set to `Required`, then all child tasks with Supported option will execute under the same transaction. Optionally you can set the TransactionOption on the Package Level and then the whole package will executin inside single transaction and whatever will fail, all the work will be rolled back. In case you need something to out of transaction control (eg. some kind of logging) then for such Control Flow items you have to set the `TransactionOption` to **`Not Supported`**. In this case such control will be executed outside the transaction scope. Be carefull when setting the `TransactionOption` to `Required` as the default **`Isolation Level`** is set to **`Serializable`**. If not used carefully you can end up with unwanted **lockingk** and performance degradation. The use of transactions needs to be analysed and designed appropriatelly especially in a case where multiple packages can operate upon single table.