"Art Corum" <com> wrote in message
The key to minimizing pressure on the procedure cache is to watch out for is
the number of different queries the application uses.
If the application is hard-coding parameter values into queries, then the
number of "different" queries the procedure cache has to manage can explode.
If all the queries are properly parameterized, then storing execution plans
for every one of them is no big deal, as an application usually only has a
couple hundred distinct queries.
Prepared queries are tricky for another reason, though. Prepared queries
are bound to the connection that ...