SQL Server Performance

ssis- job- speed

Discussion in 'SQL Server 2005 Integration Services' started by arkiboys, Dec 12, 2007.

  1. arkiboys Member

    The ssis package takes 5 seconds to complete when run from the designer.
    This ssis package is now triggered from within a scheduled job which takes 30 seconds to complete.
    I do not see why there is a difference of 25 seconds.
    Any thoughts please?
  2. Adriaan New Member

    What kind of job is it?
    Perhaps you are running it from designer just after it has completed as a scheduled job, and there is no more data to be processed? Something like that.
  3. arkiboys Member

    I created a job in sql server 2005 which runs that ssis package.
    Trying to find out why this job takes longer to complete than when the ssis package is run from the designer i.e by clicking the run button.
  4. Adriaan New Member

    We already knew that. What does the ssis package actually do?
    If you run the job from Designer just before the scheduled job will start, does it take longer?
  5. arkiboys Member

    The ssis package imports data into tables.
  6. Adriaan New Member

    On the job definition, does it wait for CPU idle time?
  7. arkiboys Member

    Not sure how to check for this but the job is scheduled to run every 2 mins at present.
  8. Adriaan New Member

    Look for the "Schedule Type" (at least that's what it's called in SQL 2000).
  9. arkiboys Member

    Do not see anything regarding this CPU idle time.

Share This Page