Home Forums SQL Server 2017 SQL Server 2017 - Administration Readable Secondary Node and Isolation Level RE: Readable Secondary Node and Isolation Level

  • December 13, 2017 at 9:43 am

    #1971984

    kevaburg - Wednesday, December 6, 2017 6:57 AM

    We have a situation here in-house whereby NOLOCK is written by default into every query.  I realise that is not a good idea but that is how it is and noone wants to change it so please don't shout at me.... 🙂

    I'm not saying a word 😀

    kevaburg - Wednesday, December 6, 2017 6:57 AM

    The point is that this behaviour (essentially a READ UNCOMMITTED statement) is overwritten by the behaviour of the HAG.  In this case it is irrelevant what the isolation level is, HAGs dictate the use of READ COMMITTED SNAPSHOT and ignores any attempts to try anything else.

    At least that is my understanding.....

    Your understanding is correct

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉