Creating a view index from scratch on a very large database (15+ GB) causes enough disk I/O to bring a pretty good-sized server to its knees. It can also cause a database to be very slow/unavailable until the index is built.
The web-based databases we create always seem to have some view that is accessed very infrequently - for example "sales categorized by sales rep then by zip code" - that gets accessed about 1/year - this causes the app to become unavailable until the view index is built (currently the longest view index discard period is 245 days).
I would like to have the option to have these indexes never discarded. Please let me manage my own disk space!