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
max12.00%
Average2.00%
System
Processor Queue Length (max)5
Processor Queue Length (avg)0
MEMORY
Pages/sec64
Available Mbytes165
Page Faults/sec546
total physical memory2096652
total sql server memory - mb1677800
Processes page fault - Sql Server0
Maximum workspace memory1243064
DISK
Disk Reads per second173
Disk Read Bytes per second11360697
Disk Writes per second20
Disk Write Bytes per second304288
SQL SERVER GENERAL STATISTICS
# connections 12
Buffer
SQL Server Buffer Manager cache hit ratio99
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
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
>
|||The Average Disk Queue length is '0'
The disk structure is like this:
Hard drive :[vbcol=seagreen]
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[vbcol=seagreen]
>news:104f301c43f59$1f8f9800$a001280a@.phx.gbl...
hard
>
>.
>
|||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...[vbcol=seagreen]
> The Average Disk Queue length is '0'
> The disk structure is like this:
> Hard drive :
> sp_who2 active show no blocking processes
> Thanks
> debby
>
> fault, however
> copying, can show up as
> in message
> hard
|||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
>
|||Debby,
Looks like you have plenty of capacity there and should be experiencing good performance. The Cache Hit Ratio for SQL is high, but that does not mean that all is well. I would suggest looking at other areas like the number of index searches per second,
full scans per second, readaheads per second and page splits per second. This will give you a quick indication of issues.
If Readaheads/sec is high (over 100), then you probably are missing an index somewhere or have a sequential process that should not run during the day. High Index scans and full scans also may indicate index issues, but you must also look at the transact
ions per second to get a good feel. Low transactions and high Index searches is not good for individual response time or scalability, while high transactions and high Index searches might be expected.
"Debby Etna" wrote:

> 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
> max12.00%
> Average2.00%
> System
> Processor Queue Length (max)5
> Processor Queue Length (avg)0
> MEMORY
> Pages/sec64
> Available Mbytes165
> Page Faults/sec546
> total physical memory2096652
> total sql server memory - mb1677800
> Processes page fault - Sql Server0
> Maximum workspace memory1243064
> DISK
> Disk Reads per second173
> Disk Read Bytes per second11360697
> Disk Writes per second20
> Disk Write Bytes per second304288
> SQL SERVER GENERAL STATISTICS
> # connections 12
> Buffer
> SQL Server Buffer Manager cache hit ratio99
> 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
>