Running a job vs code

Question

Post reply

Running a job vs code

BillOrova

SSC Rookie

Points: 33
More actions
August 16, 2019 at 2:30 pm

#3671857

Why would a scheduled job run much longer than just the code with running it in query builder the codes are identical

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

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

rVadim Hall of Fame Points: 3969 More actions · Answer 1

There was similar question recently, take a look:

https://www.sqlservercentral.com/forums/topic/job-duration-much-longer-than-step-durations

--Vadim R.

Chris Harshman SSC-Forever Points: 42192 More actions · Answer 2

Actually this is more likely a problem of the 2 different ways of running the same query having different connection properties. I'd look there first. The most impacting setting is ARITHABORT

Here's a reference for the setting, Microsoft says explicitly in their documentation to always set ARITHABORT ON, setting it to OFF can negatively impact performance:

https://docs.microsoft.com/en-us/sql/t-sql/statements/set-arithabort-transact-sql?view=sql-server-2017#remarks

Yet the default for connections is usually set to OFF. You can change what the default setting is for connections that don't explicitly set them:

https://blog.sqlauthority.com/2018/08/07/sql-server-setting-arithabort-on-for-all-connecting-net-applications/

If you can confirm the connection already is using ARITHABORT ON, then it may be time to start looking into this article:

http://www.sommarskog.se/query-plan-mysteries.html