• 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)