Benefits of making a sql server database as read-only?

Question

I am using a reporting database which for all practical purposes is a read only database. It is created data and dynamic reports are generated and viewed on this database. I was thinking of making this database as read-only.

Some of things I want to ask regarding read-only databases are

1. Is only the data read only ? Can we still create indexes or views on this database ?
2. What are the performace benefits of using a read-only database ? like, select queries using shared locks ..
3. Is there any disadvantage of using a read-only database ?
4. Any best practicse while using read-only reporting database.

Please let me know, if you need any more information.

Thanks.

Answer 1

1. You cannot make schema changes when the database is read only but you could put all your user tables on a new file group and mark that as read only.
2. You can expect a modest performance benefit from absence of locking.
3. Can't think of any.
4. Before making it read only you might as well remove all logical fragmentation and make page density as high as possible. Any non default FILL_FACTOR settings will not be of benefit in a read only environment.

Answer 2

1. The entire database is read only so you cannot add indexes or views.
2. No locking required so no locks are taken for any query other than a shared database lock. Obviously means that no blocking will occur either.
3. Not as such no.
4. None that I can suggest.