I've been given the enviable task of updating someone else's SSIS project that has been running in production for some time. There was no development server at the time it was created and no project files available so I have had to copy the dtsx files plus
any other supporting files onto my dev server.
I've battled for a few days with connection managers not wanting to update (literally change data source, save, close, open and the datasource reverted back to what it was!), interesting configurations and various other odd things.
Currently, I have two more general SSIS questions
1) When I run my current job, it gets about 30% of the way through in about 3 minutes. It then seems to wait for about another 3 minutes, apparently doing nothing, then continues before failing (see 2). Is there any way I can trace why it is pausing or what
it is doing at that time? The processor/ram seem quiet and SQL profiler doesn't tell me a lot is happening. I couldn't think of anything else. My next step would be to add some more logging but not sure where to put it!
2) My job eventually fails at a parent package (LoadDim.dtsx) which I have cut down to execute only 3 of the the child packages DIM1.dtsx, DIM2.dtsx & DIM3.dtsx. The parent Progress tab reports that DIM1.dtsx has failed so I open DIM1 and all is steps
are green and there are no err
View Complete Post