Number of concurrent SSIS jobs

  • posted similar question under sql general forum:

    http://www.sqlservercentral.com/Forums/Topic775098-149-1.aspx

    My original question was regarding large gaps between job steps within a job stream.

    What I noticed in my sysdts90 log was that multiple job streams appeared to pause for over 20 minutes between steps, steps that should have executed immediately. I'm know I read something about the number of SSIS jobs vs the number or CPU's. Looking for any suggestions - thanks

  • Are you capturing when a package starts only or when it starts and ends. I'm wondering if it is taking 20 minutes to complete that package..

    CEWII

  • capturing start and end job step. Takes a couple minutes then the next step doesn't start for 20 minutes.

  • No retries?

    CEWII

  • Also when the jobs run normally there is a short pause between steps 10 seconds or so. Now that makes me think, I should start logging pre and post validate/execute events to see if maybe, like you said the package is possible still running.

  • The job steps have 0 retries. Could you explain how this may help. Would a retry start the step even if it was going to run at a later time?

  • When you run it interactively in BIDS what does it do? Depending on how big the package is and how many objects it has to validate and where they I could see a multi-minute delay, I'm would think that 20 minutes is a bit steep..

    CEWII

  • runs fine in BIDS and when it runs normally there is a about a 10 -15 second delay between packages /job steps. After some more investigation I've seen this same behavior between an SSIS job step a T-sql job step. This may not even be related to SSIS. I did check the agent logs and there were no entries for the time frame. Have not looked at the event viewer yet, I'll do that next.

Viewing 8 posts - 1 through 7 (of 7 total)

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