Performance Monitor Results

Dear Friends,
Please take a look at this performance monitoring shots.
This server is so slow. Is something wrong with the hard
drive or the memory? What settings can I do to fix the
problem?
Thank you
Debby
PROCESSOR TIME
max 12.00%
Average 2.00%
System
Processor Queue Length (max) 5
Processor Queue Length (avg) 0
MEMORY
Pages/sec 64
Available Mbytes 165
Page Faults/sec 546
total physical memory 2096652
total sql server memory - mb 1677800
Processes page fault - Sql Server 0
Maximum workspace memory 1243064
DISK
Disk Reads per second 173
Disk Read Bytes per second 11360697
Disk Writes per second 20
Disk Write Bytes per second 304288
SQL SERVER GENERAL STATISTICS
# connections 12
Buffer
SQL Server Buffer Manager cache hit ratio 99
Hardware Info
Hard drive :
C' drive total hd space = 33.9G space
available = 20.2 G
D' drive total hd space = 273G space
available = 272G
E' drive total hd space = 273G space
available = 172 G
F' drive total hd space = 273G space
available = 127 G
F' drive total hd space = 819G space
available = 431 G
CPU = 2.80 GHz
RAM = 2.09G
Operating System = Windows 2000 SP4What is the underlying physical disk structure?
What is the average disk queue length?
Does sp_who2 show many blocked processes?
FYI, a properly tuned SQL server should almost never page fault, however
some file write operations, mostly backups or file copying, can show up as
page faults to perfmon.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Debby Etna" <anonymous@.discussions.microsoft.com> wrote in message
news:104f301c43f59$1f8f9800$a001280a@.phx.gbl...
> Dear Friends,
> Please take a look at this performance monitoring shots.
> This server is so slow. Is something wrong with the hard
> drive or the memory? What settings can I do to fix the
> problem?
> Thank you
> Debby
>
> PROCESSOR TIME
> max 12.00%
> Average 2.00%
> System
> Processor Queue Length (max) 5
> Processor Queue Length (avg) 0
> MEMORY
> Pages/sec 64
> Available Mbytes 165
> Page Faults/sec 546
> total physical memory 2096652
> total sql server memory - mb 1677800
> Processes page fault - Sql Server 0
> Maximum workspace memory 1243064
> DISK
> Disk Reads per second 173
> Disk Read Bytes per second 11360697
> Disk Writes per second 20
> Disk Write Bytes per second 304288
> SQL SERVER GENERAL STATISTICS
> # connections 12
> Buffer
> SQL Server Buffer Manager cache hit ratio 99
> Hardware Info
> Hard drive :
> C' drive total hd space = 33.9G space
> available = 20.2 G
> D' drive total hd space = 273G space
> available = 272G
> E' drive total hd space = 273G space
> available = 172 G
> F' drive total hd space = 273G space
> available = 127 G
> F' drive total hd space = 819G space
> available = 431 G
> CPU = 2.80 GHz
> RAM = 2.09G
> Operating System = Windows 2000 SP4
>|||The Average Disk Queue length is '0'
The disk structure is like this:
Hard drive :
>> C = total hd space = 33.9G space avail = 20.2 G
>> D = total hd space = 273G space avail = 272G
>> E = total hd space = 273G space avail = 172 G
>> F = total hd space = 273G space avail = 127 G
>> G = total hd space = 819G space avail = 431 G
sp_who2 active show no blocking processes
Thanks
debby
>--Original Message--
>What is the underlying physical disk structure?
>What is the average disk queue length?
>Does sp_who2 show many blocked processes?
>FYI, a properly tuned SQL server should almost never page
fault, however
>some file write operations, mostly backups or file
copying, can show up as
>page faults to perfmon.
>--
>Geoff N. Hiten
>Microsoft SQL Server MVP
>Senior Database Administrator
>Careerbuilder.com
>I support the Professional Association for SQL Server
>www.sqlpass.org
>"Debby Etna" <anonymous@.discussions.microsoft.com> wrote
in message
>news:104f301c43f59$1f8f9800$a001280a@.phx.gbl...
>> Dear Friends,
>> Please take a look at this performance monitoring shots.
>> This server is so slow. Is something wrong with the
hard
>> drive or the memory? What settings can I do to fix the
>> problem?
>> Thank you
>> Debby
>>
>> PROCESSOR TIME
>> max 12.00%
>> Average 2.00%
>> System
>> Processor Queue Length (max) 5
>> Processor Queue Length (avg) 0
>> MEMORY
>> Pages/sec 64
>> Available Mbytes 165
>> Page Faults/sec 546
>> total physical memory 2096652
>> total sql server memory - mb 1677800
>> Processes page fault - Sql Server 0
>> Maximum workspace memory 1243064
>> DISK
>> Disk Reads per second 173
>> Disk Read Bytes per second 11360697
>> Disk Writes per second 20
>> Disk Write Bytes per second 304288
>> SQL SERVER GENERAL STATISTICS
>> # connections 12
>> Buffer
>> SQL Server Buffer Manager cache hit ratio 99
>> Hardware Info
>> Hard drive :
>> C' drive total hd space = 33.9G space
>> available = 20.2 G
>> D' drive total hd space = 273G space
>> available = 272G
>> E' drive total hd space = 273G space
>> available = 172 G
>> F' drive total hd space = 273G space
>> available = 127 G
>> F' drive total hd space = 819G space
>> available = 431 G
>> CPU = 2.80 GHz
>> RAM = 2.09G
>> Operating System = Windows 2000 SP4
>
>.
>|||Disk structure = hardware layout. Space is only one issue. Spindles, type,
speed (bus and RPM), RAID layout.
Also, do you have any other applications running on this box?
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Debby" <anonymous@.discussions.microsoft.com> wrote in message
news:1052501c43f64$ec0de6b0$a301280a@.phx.gbl...
> The Average Disk Queue length is '0'
> The disk structure is like this:
> Hard drive :
> >> C = total hd space = 33.9G space avail = 20.2 G
> >> D = total hd space = 273G space avail = 272G
> >> E = total hd space = 273G space avail = 172 G
> >> F = total hd space = 273G space avail = 127 G
> >> G = total hd space = 819G space avail = 431 G
> sp_who2 active show no blocking processes
> Thanks
> debby
>
> >--Original Message--
> >What is the underlying physical disk structure?
> >
> >What is the average disk queue length?
> >
> >Does sp_who2 show many blocked processes?
> >
> >FYI, a properly tuned SQL server should almost never page
> fault, however
> >some file write operations, mostly backups or file
> copying, can show up as
> >page faults to perfmon.
> >
> >--
> >Geoff N. Hiten
> >Microsoft SQL Server MVP
> >Senior Database Administrator
> >Careerbuilder.com
> >
> >I support the Professional Association for SQL Server
> >www.sqlpass.org
> >
> >"Debby Etna" <anonymous@.discussions.microsoft.com> wrote
> in message
> >news:104f301c43f59$1f8f9800$a001280a@.phx.gbl...
> >> Dear Friends,
> >>
> >> Please take a look at this performance monitoring shots.
> >> This server is so slow. Is something wrong with the
> hard
> >> drive or the memory? What settings can I do to fix the
> >> problem?
> >>
> >> Thank you
> >> Debby
> >>
> >>
> >> PROCESSOR TIME
> >> max 12.00%
> >> Average 2.00%
> >>
> >> System
> >> Processor Queue Length (max) 5
> >> Processor Queue Length (avg) 0
> >>
> >> MEMORY
> >> Pages/sec 64
> >> Available Mbytes 165
> >> Page Faults/sec 546
> >> total physical memory 2096652
> >> total sql server memory - mb 1677800
> >> Processes page fault - Sql Server 0
> >> Maximum workspace memory 1243064
> >>
> >> DISK
> >> Disk Reads per second 173
> >> Disk Read Bytes per second 11360697
> >> Disk Writes per second 20
> >> Disk Write Bytes per second 304288
> >>
> >> SQL SERVER GENERAL STATISTICS
> >>
> >> # connections 12
> >>
> >> Buffer
> >> SQL Server Buffer Manager cache hit ratio 99
> >> Hardware Info
> >>
> >> Hard drive :
> >> C' drive total hd space = 33.9G space
> >> available = 20.2 G
> >> D' drive total hd space = 273G space
> >> available = 272G
> >> E' drive total hd space = 273G space
> >> available = 172 G
> >> F' drive total hd space = 273G space
> >> available = 127 G
> >> F' drive total hd space = 819G space
> >> available = 431 G
> >>
> >> CPU = 2.80 GHz
> >> RAM = 2.09G
> >>
> >> Operating System = Windows 2000 SP4
> >>
> >
> >
> >.
> >|||Take a look at the execution plans of your problem queries. The i/o metrics
indicate sequential scans so perhaps some index tuning is needed.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Debby Etna" <anonymous@.discussions.microsoft.com> wrote in message
news:104f301c43f59$1f8f9800$a001280a@.phx.gbl...
> Dear Friends,
> Please take a look at this performance monitoring shots.
> This server is so slow. Is something wrong with the hard
> drive or the memory? What settings can I do to fix the
> problem?
> Thank you
> Debby
>
> PROCESSOR TIME
> max 12.00%
> Average 2.00%
> System
> Processor Queue Length (max) 5
> Processor Queue Length (avg) 0
> MEMORY
> Pages/sec 64
> Available Mbytes 165
> Page Faults/sec 546
> total physical memory 2096652
> total sql server memory - mb 1677800
> Processes page fault - Sql Server 0
> Maximum workspace memory 1243064
> DISK
> Disk Reads per second 173
> Disk Read Bytes per second 11360697
> Disk Writes per second 20
> Disk Write Bytes per second 304288
> SQL SERVER GENERAL STATISTICS
> # connections 12
> Buffer
> SQL Server Buffer Manager cache hit ratio 99
> Hardware Info
> Hard drive :
> C' drive total hd space = 33.9G space
> available = 20.2 G
> D' drive total hd space = 273G space
> available = 272G
> E' drive total hd space = 273G space
> available = 172 G
> F' drive total hd space = 273G space
> available = 127 G
> F' drive total hd space = 819G space
> available = 431 G
> CPU = 2.80 GHz
> RAM = 2.09G
> Operating System = Windows 2000 SP4
>

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.
>>.
>.
>