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.

Question 1:But on another note I'm wondering if introducing Nolock in all sqls a good idea?

Question 2:Also is there an alternative to putting no lock in each and every SQL in the database?

Question 3: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).

The database I'm dealing with is not set to readonly. Application does only reads from it. We do occasional updates every month, but during that process we shut the application down.

Instead of making the db as readonly, what will be the performance implications between isolation levels READ UNCOMMITTED and READ COMMITTED SNAPSHOT isolation?Which would be better for my case?

How complex is the process to set the database as READONLY? The reason I'm asking because, our db will be deleted every couple of months and the new database version will be restored.So setting the db as READONLY after the restore will have to be repeated every single time the restore is done?Thanks!

The database I'm dealing with is not set to readonly. Application does only reads from it. We do occasional updates every month, but during that process we shut the application down.

Instead of making the db as readonly, what will be the performance implications between isolation levels READ UNCOMMITTED and READ COMMITTED SNAPSHOT isolation?Which would be better for my case?

How complex is the process to set the database as READONLY? The reason I'm asking because, our db will be deleted every couple of months and the new database version will be restored.So setting the db as READONLY after the restore will have to be repeated every single time the restore is done?Thanks!

I don't believe any of that will help. The application is "read only" and offline while you're doing the updates to the database.

Certain stored procedures are slow And need advice on what could be done given the database is readonly.

Which stored procedures? The ones that the application uses? Is it always the same stored procedures that run slow?

--Jeff Moden"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T."--22 Aug 2013

If your only currently known symptom is "some SQL statements are slow", then you need to start with the usual analysis steps even before you get to troubleshooting.

1) What is "slow"? Why? Did it used to be different? How long ago? What is a list of everything that changed over that time?2) What is "fast"? Why? Is that even reasonable (i.e. a full table scan of 25TB of data in 0.05 seconds is not reasonable... no matter how much someone wants it)3) What hardware are you on right now? Keep coming back to this to get more detail, down to the particular spindles and what shares each element, as you work through the other aspects, until it's "fast enough".4) What wait states are growing fastest when it's "slow"? "fast"?5) What SQL statements are involved? All? Some? What do they have in common? Time of day based?6) What else happens when it's "slow"? When it's "fast"? On the database? On the instance? On the hardware? On the network? On the SAN? On the user's machine?

There's a lot to look at and a lot to learn - any one "quick fix", whatever it is, will only work if that addresses most to all of your current issue. You may have a different current issue, or more than one.

Alternately, free up some budget and hire one of the many experts available, some of whom post here.