Post reply

Differing execution times, same job, different execution methods

  • May 24, 2012 at 7:58 am

    #256357

    I have a package that runs on a job server that pulls data from db2 and populates sql tables on a different server. So, data flow is db2 (odbc) thru sql job server to another sql server using linked server connection. When the package is executed from a job it runs in about 45 minutes, when I open the solution and run it, it completes in less that 10 minutes. The job server is server2008r2, sql2008r2, 64bit, 1cpu, 8gb ram. Why would this happen?

    There is an exception to every rule, except this one...

  • May 24, 2012 at 8:02 am

    #1492564

    It can be many many different things.

    Just first from my head: try to SET ARITHABORT ON for connection in your job.

    _____________________________________________
    "The only true wisdom is in knowing you know nothing"
    "O skol'ko nam otkrytiy chudnyh prevnosit microsofta duh!":-D
    (So many miracle inventions provided by MS to us...)

    How to post your question to get the best and quick help[/url]

  • May 24, 2012 at 8:25 am

    #1492589

    Not sure I understand where you're saying to set that. It's not a script, using data flow objects. Thanks for the reply.

    There is an exception to every rule, except this one...

Viewing 3 posts - 1 through 2 (of 2 total)

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