I have tables that during production hours are not wrote to, and yet during the night they can have records written. The few nights data is being wrote to the tables, users are not running queries against them.
We think we have some read blocking on longer running queries on these tables and some users are paying the price. We're considering adding nolock to these queries.
My general rule of thumb is no nolock. But I'm starting to think this might be an okay use case.
I realize I could also look at READ COMMITTED snapshot isolation but I feel like it might accomplish the same thing, but would this route use the tempdb more?