Set the sequence of caching information link.

The ability to have more control over caching information links. Currently there is no way to schedule information links to cache one after each other. The customer here would like able to set the sequence of triggered information link caching to web player. Ideally we would have a scheduler for information links that would allow us to just cache the information link at certain times/days (similar to the schedule that is already in the web player for memory caching).


Without the ability to schedule information link caching we don’t have a way to clearly separate information link caching to disk and web player memory caching of the reports to RAM. There is a need to be able to only cache to disk and not memory until the end user demands it. This helps us save in needing RAM for all information links and instead just a portion that is called on demand.
When working with large datasets information links can sometimes pull 10+ GBs of information. When this occurs Spotfire sometimes cannot read all of the data fast enough which makes SQL Server have to store this data in TempDB. Ideally Spotfire would be able to read this information fast enough in all cases, but there are cases where it can’t. When too much data is stored in TempDB it can cause the drive to fill up and our entire system to go offline. To avoid TempDB with filling up with too much information we would like the ability to schedule information links so that another information link does not attempt to cache until the other one is completely done and read by Spotfire. We have 20+ Information Links that need to cache each morning so if there is a hold up with Spotfire sometimes all of these information links get held up in TempDB.