SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Job getting stuck in UAT but runs fine in Prod


Job getting stuck in UAT but runs fine in Prod

Author
Message
coolchaitu
coolchaitu
SSCarpal Tunnel
SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)

Group: General Forum Members
Points: 4343 Visits: 1387
  • 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
    Lynn Pettis
    SSC Guru
    SSC Guru (223K reputation)SSC Guru (223K reputation)SSC Guru (223K reputation)SSC Guru (223K reputation)SSC Guru (223K reputation)SSC Guru (223K reputation)SSC Guru (223K reputation)SSC Guru (223K reputation)

    Group: General Forum Members
    Points: 223055 Visits: 40397
    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?

    Cool
    Lynn Pettis

    For better assistance in answering your questions, click here
    For tips to get better help with Performance Problems, click here
    For Running Totals and its variations, click here or when working with partitioned tables
    For more about Tally Tables, click here
    For more about Cross Tabs and Pivots, click here and here
    Managing Transaction Logs

    SQL Musings from the Desert Fountain Valley SQL (My Mirror Blog)
    HappyGeek
    HappyGeek
    SSCertifiable
    SSCertifiable (6.8K reputation)SSCertifiable (6.8K reputation)SSCertifiable (6.8K reputation)SSCertifiable (6.8K reputation)SSCertifiable (6.8K reputation)SSCertifiable (6.8K reputation)SSCertifiable (6.8K reputation)SSCertifiable (6.8K reputation)

    Group: General Forum Members
    Points: 6799 Visits: 4400
    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
    sqlgeekspro
    Forum Newbie
    Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)

    Group: General Forum Members
    Points: 3 Visits: 24
    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
    Jeff Moden
    SSC Guru
    SSC Guru (505K reputation)SSC Guru (505K reputation)SSC Guru (505K reputation)SSC Guru (505K reputation)SSC Guru (505K reputation)SSC Guru (505K reputation)SSC Guru (505K reputation)SSC Guru (505K reputation)

    Group: General Forum Members
    Points: 505421 Visits: 44253
    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.
    If you think its expensive to hire a professional to do the job, wait until you hire an amateur. -- Red Adair

    Helpful Links:
    How to post code problems
    How to post performance problems
    Forum FAQs
    Jeff Moden
    Jeff Moden
    SSC Guru
    SSC Guru (505K reputation)SSC Guru (505K reputation)SSC Guru (505K reputation)SSC Guru (505K reputation)SSC Guru (505K reputation)SSC Guru (505K reputation)SSC Guru (505K reputation)SSC Guru (505K reputation)

    Group: General Forum Members
    Points: 505421 Visits: 44253
    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.
    If you think its expensive to hire a professional to do the job, wait until you hire an amateur. -- Red Adair

    Helpful Links:
    How to post code problems
    How to post performance problems
    Forum FAQs
    Arsh
    Arsh
    SSCrazy
    SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)

    Group: General Forum Members
    Points: 2190 Visits: 822
    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
    coolchaitu
    SSCarpal Tunnel
    SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)

    Group: General Forum Members
    Points: 4343 Visits: 1387
    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
    Jeff Moden
    SSC Guru
    SSC Guru (505K reputation)SSC Guru (505K reputation)SSC Guru (505K reputation)SSC Guru (505K reputation)SSC Guru (505K reputation)SSC Guru (505K reputation)SSC Guru (505K reputation)SSC Guru (505K reputation)

    Group: General Forum Members
    Points: 505421 Visits: 44253
    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.
    If you think its expensive to hire a professional to do the job, wait until you hire an amateur. -- Red Adair

    Helpful Links:
    How to post code problems
    How to post performance problems
    Forum FAQs
    coolchaitu
    coolchaitu
    SSCarpal Tunnel
    SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)

    Group: General Forum Members
    Points: 4343 Visits: 1387
    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

    Go


    Permissions

    You can't post new topics.
    You can't post topic replies.
    You can't post new polls.
    You can't post replies to polls.
    You can't edit your own topics.
    You can't delete your own topics.
    You can't edit other topics.
    You can't delete other topics.
    You can't edit your own posts.
    You can't edit other posts.
    You can't delete your own posts.
    You can't delete other posts.
    You can't post events.
    You can't edit your own events.
    You can't edit other events.
    You can't delete your own events.
    You can't delete other events.
    You can't send private messages.
    You can't send emails.
    You can read topics.
    You can't vote in polls.
    You can't upload attachments.
    You can download attachments.
    You can't post HTML code.
    You can't edit HTML code.
    You can't post IFCode.
    You can't post JavaScript.
    You can post emoticons.
    You can't post or upload images.

    Select a forum








































































































































































    SQLServerCentral


    Search