Odd problem with Profiler

I wonder if anyone here knows what the problem is.
On one server that I administer, when running a Profiler trace (either
through the GUI or directly using the stored procs) the “Reads” column a
lways
returns 0 no matter what event is being monitored.
The server runs SQL 2000 Enterprise Edition sp3 on Win 2000 sp4.
Thanks in advance,
AntoIrishAnto wrote:
> I wonder if anyone here knows what the problem is.
> On one server that I administer, when running a Profiler trace (either
> through the GUI or directly using the stored procs) the “Reads”
> column always returns 0 no matter what event is being monitored.
> The server runs SQL 2000 Enterprise Edition sp3 on Win 2000 sp4.
> Thanks in advance,
> Anto
I saw this reported once on a customer who used EMC disks and broke a
cluster to make two stand-alone installs of SQL Server. That's when the
read statistics were no longer were captured. I can't say I remember
what the solution was.
David Gugick
Quest Software
www.imceda.com
www.quest.com|||"David Gugick" wrote:

> IrishAnto wrote:
> I saw this reported once on a customer who used EMC disks and broke a
> cluster to make two stand-alone installs of SQL Server. That's when the
> read statistics were no longer were captured. I can't say I remember
> what the solution was.
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>
The server in question was never part of a cluster. As far as I'm aware
profiler used to return values in the reads column, but no longer.
I've seen other message boards with the same problem posted, but with no
answers. I was hoping someone at Microsoft might know of a solution.
Anto|||IrishAnto wrote:
> The server in question was never part of a cluster. As far as I'm
> aware profiler used to return values in the reads column, but no
> longer. I've seen other message boards with the same problem posted,
> but with no answers. I was hoping someone at Microsoft might know of
> a solution.
>
This is likely not a Profiler issue, but a SQL Trace API one on the
server. I assume the problem occurs from all clients, including the
server itself.
I might consider opening a support case with Microsoft... and then
sharing the solution with the rest of us :-)
In any case, I assume you are running SP3a or SP4 on the server. Is that
correct?
David Gugick
Quest Software
www.imceda.com
www.quest.com|||"David Gugick" wrote:

> IrishAnto wrote:
> This is likely not a Profiler issue, but a SQL Trace API one on the
> server. I assume the problem occurs from all clients, including the
> server itself.
> I might consider opening a support case with Microsoft... and then
> sharing the solution with the rest of us :-)
> In any case, I assume you are running SP3a or SP4 on the server. Is that
> correct?
>
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>
David,
Indeed we’re running Sp3a on a Win 2000 Sp4 box.
It would seem that the Trace API is no longer functioning correctly, so the
only solution maybe a call to Microsoft.
Thanks for your reply anyway.
Anto