performance monitor counters

I have a windows 2000 sp4 server running sql 2000 sp3.
The server only has one drive - drive 'C' with 101G, used
space = 31.5g and free space = 70.1gigs.
I like to monitor the following counters in performance
monitor:
Memory: Available Bytes
Memory: Pages/sec
Process: Working Set
SQL Server: Buffer Manager: Buffer Cache Hit Ratio
SQL Server: Buffer Manager: Total Pages
SQL Server: Memory Manager: Total Server Memory (KB)
PhysicalDisk: % Disk Time
PhysicalDisk: Avg. Disk Queue Length
Processor:% Processor Time
System: %Total Processor Time
Processor: % Privileged Time
Processor: %User Time
System: Processor Queue Length
Which ranges are normal when the server is not performing
anything extensive?
I appreciate your help with this information because know
how to monitor a server is one thing - but know what is
too high or too low is another thing which I need help
with. Thank you.It depends. YOu need to have a normal baseline for your
systems to be able to tell what is abnormal for your
systems. If you never established such a thing, it's
educated guesses beyond that.
Some things are more absolute. For example, if you have
sustained disk queue lengths (usually above 3), you are
more than likely disk bound, or something funky is going
on (i.e. you may need to rebuild indexes ... but check
first).
Again, I can't stress enough that you need to know a
baseline before you go into production to determine what
is normal for you and what is not.
>--Original Message--
>I have a windows 2000 sp4 server running sql 2000 sp3.
>The server only has one drive - drive 'C' with 101G, used
>space = 31.5g and free space = 70.1gigs.
>I like to monitor the following counters in performance
>monitor:
>Memory: Available Bytes
>Memory: Pages/sec
>Process: Working Set
>SQL Server: Buffer Manager: Buffer Cache Hit Ratio
>SQL Server: Buffer Manager: Total Pages
>SQL Server: Memory Manager: Total Server Memory (KB)
>PhysicalDisk: % Disk Time
>PhysicalDisk: Avg. Disk Queue Length
>Processor:% Processor Time
>System: %Total Processor Time
>Processor: % Privileged Time
>Processor: %User Time
>System: Processor Queue Length
>Which ranges are normal when the server is not performing
>anything extensive?
>I appreciate your help with this information because know
>how to monitor a server is one thing - but know what is
>too high or too low is another thing which I need help
>with. Thank you.
>.
>|||Hi
You may want to invest in:
SQL Server 2000 Performance Turning Technical Reference ISBN 0-7356-1270-6
Which talks about how to calculating/evaluating wether the values you have
are good or bad.
John
"Regina Styles" <anonymous@.discussions.microsoft.com> wrote in message
news:077b01c3d149$91ec8300$a601280a@.phx.gbl...
> I have a windows 2000 sp4 server running sql 2000 sp3.
> The server only has one drive - drive 'C' with 101G, used
> space = 31.5g and free space = 70.1gigs.
> I like to monitor the following counters in performance
> monitor:
> Memory: Available Bytes
> Memory: Pages/sec
> Process: Working Set
> SQL Server: Buffer Manager: Buffer Cache Hit Ratio
> SQL Server: Buffer Manager: Total Pages
> SQL Server: Memory Manager: Total Server Memory (KB)
> PhysicalDisk: % Disk Time
> PhysicalDisk: Avg. Disk Queue Length
> Processor:% Processor Time
> System: %Total Processor Time
> Processor: % Privileged Time
> Processor: %User Time
> System: Processor Queue Length
> Which ranges are normal when the server is not performing
> anything extensive?
> I appreciate your help with this information because know
> how to monitor a server is one thing - but know what is
> too high or too low is another thing which I need help
> with. Thank you.
>|||I appreciate your response. This is all in development
and I don't need to do anything in production. I am
really in a learning phase right now. Do you have an
average of what is good for a server with nothing running
other than sql and may be one application that is not
doing much to the databases at all?
Thanks.
>--Original Message--
>It depends. YOu need to have a normal baseline for your
>systems to be able to tell what is abnormal for your
>systems. If you never established such a thing, it's
>educated guesses beyond that.
>Some things are more absolute. For example, if you have
>sustained disk queue lengths (usually above 3), you are
>more than likely disk bound, or something funky is going
>on (i.e. you may need to rebuild indexes ... but check
>first).
>Again, I can't stress enough that you need to know a
>baseline before you go into production to determine what
>is normal for you and what is not.
>>--Original Message--
>>I have a windows 2000 sp4 server running sql 2000 sp3.
>>The server only has one drive - drive 'C' with 101G,
used
>>space = 31.5g and free space = 70.1gigs.
>>I like to monitor the following counters in performance
>>monitor:
>>Memory: Available Bytes
>>Memory: Pages/sec
>>Process: Working Set
>>SQL Server: Buffer Manager: Buffer Cache Hit Ratio
>>SQL Server: Buffer Manager: Total Pages
>>SQL Server: Memory Manager: Total Server Memory (KB)
>>PhysicalDisk: % Disk Time
>>PhysicalDisk: Avg. Disk Queue Length
>>Processor:% Processor Time
>>System: %Total Processor Time
>>Processor: % Privileged Time
>>Processor: %User Time
>>System: Processor Queue Length
>>Which ranges are normal when the server is not
performing
>>anything extensive?
>>I appreciate your help with this information because
know
>>how to monitor a server is one thing - but know what is
>>too high or too low is another thing which I need help
>>with. Thank you.
>>.
>.
>