>>Source of the request imakes no difference.
>>
>>A few years ago I designed a medical reporting system (VFP+SQL2005) that had huge history tables (one was over 100 GIG by itself) that would uncache after hours and take the first user in the morning a well over a minute to retrieve data from (and milliseconds afterwards).
>>
>>I made a little VFP app that ran as a scheduled task several times nightly that just did a quick select on all the large tables - this fixed the issue.
>>
>>I think if I needed to do it now I'd probably use the PINTABLES approach.
>
>So, you ended up in the same scenario I have now.
>
>But, using PINTABLES is something that is invisible to the developer once done. By that, I mean that if it is applied, then a migration to another server occurs, we could loose that and face the same situation later on on the new server. Well, there is a well detailed documentation but my experience is that many do not read it. I believe what you have done is what I am mostly interesting in. You mentioned you were doing a SQL select. So, even if that ocurred on an update command, if I run a SQL select during the overnight period, will that also make the update command aware of it and avoid such a situation?

Just did a search for more info on PINTABLE and found that it no longer does *ANYTHING* in SQL2008. The command simply exists for backwards compatibility. Apparently Microsoft had too many problems related to using the command so it is no longer functional.

That crosses that off the list of options.