Job getting stuck in UAT but runs fine in Prod

Question

Job getting stuck in UAT but runs fine in Prod

coolchaitu

SSChampion

Points: 10334
More actions
December 4, 2017 at 10:03 am

#326729
Good Morning Experts
One of our jobs is getting stuck everytime it is triggered in UAT. The same ,job is running fine in prod. The job runs sql code.Could you please let me know how to approach this issue,why is job getting stuck each time it is being triggered in UAT

Lynn Pettis SSC Guru Points: 442467 More actions · Answer 1

coolchaitu - Monday, December 4, 2017 10:03 AM
Good Morning Experts
One of our jobs is getting stuck everytime it is triggered in UAT. The same ,job is running fine in prod. The job runs sql code.Could you please let me know how to approach this issue,why is job getting stuck each time it is being triggered in UAT

Does the code run fin in UAT when run in SSMS?

HappyGeek SSCoach Points: 18729 More actions · Answer 2

I would be more worried about why it has not passed in UAT and yet and yet has been released to production! Has something changed in the UAT environment since the code was released to production?

...

sqlgeekspro Grasshopper Points: 17 More actions · Answer 3

Have you checked if the job is getting blocked by other queries/jobs in UAT.
I also wonder how it is passed UAT if it was not working and released to Prod?

Dev
http://sqlgeekspro.com/

Jeff Moden SSC Guru Points: 1004307 More actions · Answer 4

HappyGeek - Monday, December 4, 2017 11:10 AM
I would be more worried about why it has not passed in UAT and yet and yet has been released to production!

+ One bazillion to THAT!

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Jeff Moden SSC Guru Points: 1004307 More actions · Answer 5

coolchaitu - Monday, December 4, 2017 10:03 AM
Good Morning Experts
One of our jobs is getting stuck everytime it is triggered in UAT. The same ,job is running fine in prod. The job runs sql code.Could you please let me know how to approach this issue,why is job getting stuck each time it is being triggered in UAT

Step one, of course, would be to define what you mean by "getting stuck". Is it the job that's getting stuck because of something wonky on the server or is it the code in the job that's getting stuck? Did someone mess up and shrink the database which will cause these types of symptoms? Does the code have a "spill to disk" somewhere because the system is underpowered compared to the production box? Like Lynn asked, does the code in the job run correctly if you run it from SSMS without the job? Are stats up to date? Etc, etc, etc. Start somewhere and expand. First thing to do is make sure that the code the job is running runs fine without the job.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Arsh SSCertifiable Points: 6354 More actions · Answer 6

Is the infrastructure(Memory/Processors etc.) for UAT at the same level as for production ? If at lower level , this can also be an issue.

coolchaitu SSChampion Points: 10334 More actions · Answer 7

Arsh - Friday, December 8, 2017 7:37 AM
Is the infrastructure(Memory/Processors etc.) for UAT at the same level as for production ? If at lower level , this can also be an issue.

The versions are different. Could that be a reason. Execution plans vary, correct

Jeff Moden SSC Guru Points: 1004307 More actions · Answer 8

coolchaitu - Friday, December 8, 2017 7:42 AM
Arsh - Friday, December 8, 2017 7:37 AM
Is the infrastructure(Memory/Processors etc.) for UAT at the same level as for production ? If at lower level , this can also be an issue.
The versions are different. Could that be a reason. Execution plans vary, correct

Versions of what? SQL Server? If so, I strongly recommend that you bring the UAT box up to the same level of SQL Server as the Production box. If the UAT box is at a higher level, then you should either role it back to what the Production box is or, better yet, bring the Production level up to the latest SP and CU (it's important for security, as well).

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

coolchaitu SSChampion Points: 10334 More actions · Answer 9

Jeff Moden - Friday, December 8, 2017 7:49 AM
coolchaitu - Friday, December 8, 2017 7:42 AM
Arsh - Friday, December 8, 2017 7:37 AM
Is the infrastructure(Memory/Processors etc.) for UAT at the same level as for production ? If at lower level , this can also be an issue.
The versions are different. Could that be a reason. Execution plans vary, correct
Versions of what? SQL Server? If so, I strongly recommend that you bring the UAT box up to the same level of SQL Server as the Production box. If the UAT box is at a higher level, then you should either role it back to what the Production box is or, better yet, bring the Production level up to the latest SP and CU (it's important for security, as well).

Thanks Jeff