No, it is not disk space.. it is not table corruption either..
it is server confusion, with no diagnostic information output.
Symptom again: hang on straight forward queries involving a total
index scan, with either count(*) or distinct(*), usually
stuck with 100% cpu use of the thread in 'sendi
Justin wrote:
>
> I have a puzzle..
>
> Frequently, about, weekly? our data server gets into a state
> where
> select distinct(keyfield) from table
> hangs in the 'sending data' phase, or the 'sorting result' phase,
> the client is left waiting for the result, no rows are returned,
> no errors
I have a puzzle..
Frequently, about, weekly? our data server gets into a state
where
select distinct(keyfield) from table
hangs in the 'sending data' phase, or the 'sorting result' phase,
the client is left waiting for the result, no rows are returned,
no errors are in the sql server error log
