Ideal settings for "read only" table I'm building an application where a certain group of programmatically-created Azure SQL Server tables will only ever be read from.

The app will create a new table, insert a bunch of data, and then serve queries from that data. After the initial inserting the data will never be changed in any way.

Given this usage pattern, are there efficiencies I could take advantage of when setting up such a table, or the indexes on it?
Rebuild indexes with a FILLFACTOR 100 so pages are packed as tight as possible.  
Update statistics on the table WITH FULLSCAN so the query optimizer has the most complete information possible to generate a query plan.