Nolock/isolation level - READONLY database
Posted on 2012-09-15
We have a sole readonly database which is updated monthly at night during maintenance window. The db has several stored procedures from simple to with medium complexity.
Certain stored procedures are slow And need advice on what could be done given the database is readonly.
The stored procedures do have Set NoCount On.
I'm looking at possible indexes that cold be added to tables.
But on another note I'm wondering if introducing Nolock in all sqls a good idea?
Also is there an alternative to putting no lock in each and every SQL in the database?
Would READ COMMITTED SNAPSHOT isolation level be an alternative for Nolock given the database is READONLY (database itself is not set to READONLY. The applications accessing the database will only read from it and will not right to it ever).