Does anyone know what the net effect of having a block of t-sql with a transaction isolation level of repeatble read and then inside having a select with nolock.
Does the nolock become invalid because the isolation level has already been set?
The table hint in the query takes precedence, as I would have expected.
Here's my test script:
In other words, setting the isolation level on the transaction makes that isolation level the default within the transaction, but that default can still be overridden by table hints, as I demonstrated.