Hi - I think that we may have an issue with our isolation level or
transaction commits in our main load package. Basically we get zipped flat
file extracts for 94 districts, then we enter a container that bulkloads
about 300 tables for each district received, loops back and then after all
districts are in a working db, another container is entered that inserts the
data into production. What I am seeing is if we get more than 20 districts
the pkg slows to a crawl (running 15 hours now!) and when you look at the
activity on the server you see thousands of open processes, one for each task
, even the ones that should have completed - once the pkg finally finishes
they all close out and all is well. My questions - 1) could the isolation
level of the package be causing this, and why is the default serializable,
and 2) where would you change it, on each task or the container or the top
level of the SSIS package? It seems we have something set very poorly or
designed wrong! Any info is greatly appreciated!
--
John F.

Hmm, in doing more research I am reading thru my big red SSIS book and
thinking this may be an issue with threading not being set properly rather
than transactions - the data commits as it should but every thread for the
entire package remains unti, the entire package completes which I think is
whats killing performance... anyone?? Bueller?
--
John F.


"John F." wrote:

*Everyone* - I think there is a hotfix that addresses this and performance of
SSIS on 64 bit in general - http://support.microsoft.com/kb/918222/ I'll
give it a shot and let y'all know.
--
John F.


"John F." wrote: