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?

Thanks!