• Sean Lange (4/24/2014)


    Eirikur Eiriksson (4/24/2014)


    How about using the TABLOCK hint?

    ๐Ÿ˜Ž

    That seems to be dealing with the symptom rather than the cause. ๐Ÿ˜‰

    Hints should be used as a last resort. The concurrency issue is caused by poor design, we shouldn't need to resort to query hints to deal with it. Just my 2ยข.

    I agree that one should not try to outsmart the query engine and the optimizer but I believe that not all hints are equal in this sense. If the problem is as described, more than one process reading the value at the same time, then force them to queue. An improved design would probably be a better solution though:cool: