When my ADO based app accesses SQL2K server at first time (i.e. there was no
any
_read/select_ access to the server for some time: 1 or more days) and runs
a SELECT query, an execution time is much longer than a time spent for
_next_ queries.
Even if the next queries use different tables and fields (in WHERE).
The underlying tables are constantly updated, e.g. every 10 minutes new
records are
inserted.
Any ideas to increase performance of first queries?
SQL Server >> SQL2K first access
Sounds like a caching related problem. You should be using stored
procedures for your data access code in order to minimize this sort of
thing.