I have a pretty simple DTS package that has 2 transformations, batch and
detail records from one database to another on the same server. It's failing
on the detail transformation with the error 'Transaction context in use by
another session' in the error log. It's only failing if the rowcount is
large. I thought KB article 279857 was close to addressing my scenario, but
I'm not sure.
Am I approaching the problem correctly? Is there something wrong with
attempting multiple transformations (same source/destination)? Are they
synchronous or asynchronous? If synchronous, how do you order the
transformations, i.e. the detail can not begin until the batch header has
completed? And should all transformations have 'join the transaction if
present' checked or unchecked? If asynchronous, do I need multiple package
connections to the same source and destination?
Any help or ideas will be greatly appreciated. Thanks!
-lenny

In article <OhGR06CnEHA.2616 (AT) tk2msftngp13 (DOT) phx.gbl>, Lenny wrote:

Usually when I see this it is because the same connection onject is being used
multiple times in the same task so an example would be using the destination
connection as a lookup connection.

Make sure you have seperate connection objects for each thing in a datapump.
You can reuse connections in different tasks though with no problem.


--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.konesans.com - Consultancy from the people who know