title: tips for optimizing a read-only sql database
body: <p>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 consider given this scenario?  Or should I just stick with the normal rules for optimizing a database?</p>