SSIS Package Isolation Level

  • 1) We are doing data migration from SQL Server 2000 OLTP design to SQL Server 2005 OLAP design.

    2) We have used SSIS packages and data flow tasks in which we mentioned connection strings for source and target containers.

    3) We have a master execute package which contains series of execute packages in relational order.

    4) Is it enough to set isolation level of master package to READUNCOMMITED and keep TransactionOption as Independent for it and supported for the rest i.e. the method used to maintain transaction integrity OR we need to make it READUNCOMMITED for each & every execute and data flow task packages.

  • "4) Is it enough to set isolation level of master package to READUNCOMMITED and keep TransactionOption as Independent for it and supported for the rest i.e. the method used to maintain transaction integrity OR we need to make it READUNCOMMITED for each & every execute and data flow task packages."

     

    This is somewhat related to your question about Transactions and packages.

    If you want commit the data for all tasks or 0 tasks if only one of them fails, then you need to group your tasks in a Sequence Container. 

    If you set transaction and isolation levels for each Data Flow task, then the data managed by that task will be within affected by those properties, however those statements will not apply to any of the other data flow tasks even if they are connected with precedence constraints.

     

     

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply