Scheduled updates to load files into memory is not always the single best solution to facilitate fast loading of data from slow data sources.
It cost a lot of instance memory and there is a need to monitor usage to prevent blind investments/costs for resources.
Using Automation Services and scripting to save an embedded copy of the file into the library is often mentioned as a solution that cost a lot less resources (compressed space on disk compared to RAM, and only Instance memory when being used) and in many cases have loading times that is not that long.
Why not make it as easy as the rules/schedules for Scheduled Updates?
As long as the resulting file have the same GUID links to it will work seamlessly after updates etc.
Implemented in | 10.0 |