Hi all,
I was wondering if anyone had any further insight as to why the query plan
would have changed so dramatically between queries, even when isolated by a
transaction?
Is it possible for database statistics to change after a query has been run
(independent of transactions)?
Thanks in advance
Some more information on this:
>
> > I say "hang", where really I've given up after ~12 hours execution. The
> > exact same query can then be terminated and run in <90 seconds, with none
> > of the underlying data changing.
>
> But does the plan change?
>
>
As it turns out it does. Some further ex
Fenn Bailey writes:
> I'm experiencing an issue where certain queries appear to
> non-deterministically "hang", with a CPU pinned at 100%.
> I say "hang", where really I've given up after ~12 hours execution. The
> exact same query can then be terminated and run in <90 seconds, with none
> of the
Hi all,
I'm experiencing an issue where certain queries appear to
non-deterministically "hang", with a CPU pinned at 100%.
I say "hang", where really I've given up after ~12 hours execution. The
exact same query can then be terminated and run in <90 seconds, with none
of the underlying data chang
