>The three counters that I provided are the basics for the three main components on the computer: processor, memory, and disk. Disk Queue Length is a measure of the number of IO requests that are required but not yet handled by the IO subsystem. I've seen remarks that anything above 2 signifies a bottleneck in the disk IO subsystem.
>
>If the Interrupts/Sec is really high, there may be a component of the system that is defective and causing a lot of interrupts which distracts the processor(s) from SQL Server.
>

I don't know what "very high" is, but it is sitting at 200/sec normally, and goes up to 600/sec when I am running the query. Now to figure out what is causing the interrupts. NIC card? Don't know.

Memory reads spiked momentarily on the first query, but repeat queries of the same page produced no changes, as one would expect if it were cached.

Am having trouble getting the logical disk running. Apparently you need to run a command-line switch to see that, and I just tried briefly before settling down with the other two. Will now try again.

>Unfortunately, in a situation like this, you have to start very wide and narrow the search once you start getting some information.
>
>-Mike