0

I am working n a SSIS package that has many Execute SQL tasks running in parallel. Each Task contains MERGE SQL statements. The parent table merge statements runs first and then all the child tables' merge statements run in parallel. The package uses the native transaction capabilities. I have designed the package such that the transaction level is set as "Required" on the control flow level and "Supported" on all other containers/executables.

The problem is, it works fine sometimes but other times it throws the following exception

ERROR Message:Transaction context in use by another session.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

What could be the reason? Does Isolation level has any impact? It's set as "Serializable" everywhere in the package. Retain Same Connection Property is also set to True.

billinkc
  • 59,250
  • 9
  • 102
  • 159
InTheWorldOfCodingApplications
  • 2,526
  • 6
  • 46
  • 87
  • http://www.mssqltips.com/sqlservertip/1585/how-to-use-transactions-in-sql-server-integration-services-ssis/ describes the SSIS transaction handling in detail. – milivojeviCH Jan 02 '13 at 17:33
  • And some more tips from MSDN: http://msdn.microsoft.com/en-us/library/ms137690.aspx – milivojeviCH Jan 02 '13 at 17:34

0 Answers0