Thanks for your response.
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?
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?
is pronounced ree-bar and is a Modenism for R
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.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is usually not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs