Post reply

Best Practice while writing Insert statement in Procedures

  • March 24, 2019 at 10:54 am

    #383227

    In our application we have lots of procedures and most of them use insert and update statement. In few cases we used merge but most of the time we faced deadlock issues, to avoid deadlock and slowness of application what are the steps that we need to take care and can suggest any best practice while writing the procs

  • March 24, 2019 at 4:02 pm

    #2025313

    Step one would be to post the code that you're found causing the deadlocks.
    Step two would be to include the deadlock chart when you do step one above.

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

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

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