Re: Weird one.
- From: "Mary Chipman [MSFT]" <mchip@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 08 Aug 2005 18:06:52 -0400
It's likely the result of the way SQLS handles query execution plan
caching. The first time a query runs, it takes longer. Subsequent
executions are faster because the plan is reused. See the topic
"Execution Plan Caching and Reuse" in SQL Server Books Online for more
information. One workaround to avoid the first-time perf hit is on
startup to run those queries in the background so plans are cached and
available for reuse. This may or may not work depending on the type of
applicaton you have.
--Mary
On Mon, 8 Aug 2005 12:01:27 -0400, "Shawn" <shawn.camner@xxxxxxxx>
wrote:
>I have a dataset named "dsMessages" that has a single table. I have a timer
>that runs a query against an SQL db every 5 seconds. At the beginning I have
>it run dsMessages.Clear(). The first time this runs, it causes a long pause,
>but then it runs fine every time thereafter. I have other datasets in the
>application that seem to do the same thing... Any ideas?
>
.
- References:
- Weird one.
- From: Shawn
- Weird one.
- Prev by Date: RE: Unable to delete row
- Next by Date: Re: weird error upon form loading
- Previous by thread: Weird one.
- Next by thread: Re: Weird one.
- Index(es):
Relevant Pages
|