Hi intersting one here...

Have a client running SQL Server 2005. We supply them with an in house toolkit which is made up of some data and some API's for accessing said data.

I have no idea why but each night they have to restart their server thus dumping the cache and when they're back online the API's are running slower as they will all be running for the first time.

I'm writing a document explaining all about the caching of the query plans etc and wanted to include if any such thing existed potential work arounds for them to perhaps store the cache somewhere then reload it after a restart.

Does anyone have any ideas?