|
16 GB is a large database. The key here is to try and keep views as small as possible, and keep the data refreshes to a minimum. A large database that is receiving numerous changes all day will never be a performance star. You need to try and break up views to keep them from growing too large, and you should try staging changes to the database on a separate server or database. Then, you can release the changes in an orderly fashion and keep the views fresh. Other than that, you should look at your hardware to make sure there aren't any I/O bottlenecks.
Do you have comments on this Ask the Expert question and response? Let us know.
|
