ReadUncommitted and NOLOCK have the same effect. Only difference is that specifying SET TRANSACTION ISOLATION LEVEL READUNCOMMITTED affects every single table within a select statement until the connection closes or a different isolation level is specified. NOLOCK applies just to the table the hint follows.
Maybe I'm missing something, but if you have virtually no updates, you shouldn't have any blocking. Select statements don't block other select statements, unless strange locking hints are applied. What's the cause of the blocking?
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)SQL In The Wild
: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter
We stand on the bridge and no one may pass