tips for optimizing a read-only sql database

Question

I have a mid-sized SQL Server 2008 database that has actuarial data in it. All of the use cases for it are read-only queries. Are there any special optimizations I should cons

Answer 1

If it is read only, one thing that you can do is put indexes on just about anything that might help (space permitting). Normally adding an index is a trade-off between a performance hit to writes and a performance gain for reads. If you get rid of the writes it's no longer a trade-off.

When you load the database you would want to drop all/most of the indexes, perform the load, then put the indexes back on the tables.