Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
blakmk
Starting Member
45 Posts |
 Posted - 2008-07-31 : 09:11:37
|
| I have a 64bit windows 2003 server running 32 bit sql 2000 with AWE set. After having upgraded the memory to 16Gb (from 8Gb), performance is still quite bad and the page life expectancy is still quite bad 50-200s. Howeber the buffer cache hit ratio is quite high giving a value of around 99% on average. This seems slightly contradictory but im not sure why its happening.Does anyone have any ideas? |
|
|
mcrowley
Aged Yak Warrior
771 Posts |
Posted - 2008-07-31 : 16:06:24
|
| Not sure memory is the problem, then. How much memory does the SQL Server process take up in Task Manager? Also have a look at the CPU usage, System - Processor Queue Length, and Avg Disk Queue Length to see if one of those is a bottleneck. |
 |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-07-31 : 16:35:33
|
| First of all it's bad to run 32-bit SQL server on 64-bit platform. Did you set min and max memory after enabling awe? |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-07-31 : 22:39:47
|
| And did you give sql service account 'lock pages in memory' user rights? |
|
|
|
|
|
|
Low page life expectancy high buffer cache hit rat