Home Forums SQL Server 2012 SQL 2012 - General Mysterious deadlocks on a heap table RE: Mysterious deadlocks on a heap table

  • July 5, 2014 at 10:45 am

    #1727164

    GilaMonster (7/5/2014)

    Jeff Moden (7/4/2014)

    Do you see any disparity between the ad-hoc code data-types and the table data-types that just might cause some unnecessary implicit conversions?

    No, Char and varchar are fine together and lengths don't cause implicit conversion problems.

    I'll have to disagree with that especially on the personal experience level especially where the CHAR data-type is involved. Unfortunately, I can't demonstrate the "personal experience" portion of that because I had them fix it and moved on. I did, however, find an article a couple of months back that had code that demonstrated the problem. Now all I have to do is find the bloody thing. :pinch:

    I've bookmarked this post. When I find the article and can demonstrate the problem, I'll post back.

    {EDIT} See my next post... I can't find the article and I can't recreate the problem so I have to retract this assertion until I can offer proof in code. My apologies, folks.

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