SQL 2005 X64 and Windows 2008 Server SP1 Performance issues
Hi I'm hoping someone can help here as we experiencing very slow performance rates running SQL on this platform
We are running SQL 2005 Sp3 x64 (9.00.4035.00) on Windows 2008 Server Standard SP1 X64 platform. The hardware is a IBM X3650 2U raid 5 , Total capacity 1.6 TB of disk (OS and Data partitioned) with 16gb of ram.
In hindsight, i would think disk i/o could be part of the issue with this raid type but i wouldn't imagine it is the key contributing factor to it but i could be wrong ?
Read 9.2/sec
Writes 7.4/sec
As this server has been reporting memory exception errors when running some reports I'm uncertain of whether any of the following statements apply to my situation ? (I'm not a SQL DBA)
Does SQL by design grab all the memory, releasing to the operating system only when it comes under pressure ?
Memory from the taskmgr consistently fluctuates around 15-15.6 gig, leaving only a small portion for the OS
Does the following cumulitative update apply to me >>http://support.microsoft.com/default.aspx/kb/970070/
Should I apply the update to SQL Standard so that i can get support for lock pages ?
Running Performance and Reliability states memory is 98% and busy (red dot) i'm assuming this is not normal , the processing appears to be fine
Memory Buffer: Page life expectancy counter can run anywhere up to 10,800,00 and sit there, I believe the calculation is 300sec = 5 mins so i'm not sure what this number translates to whether I am reading it wrong or it's reporting 180mins ?
Stats at 12:00pm today
Available MBytes 223.000
Pages Input/sec 0.000
Pages/sec 0.000
Buffer cache hit ratio 99.873
Page life expectancy 3,630.000
Is it a network bottleneck as this server uses broadcom BCM5708C NetXtreme II GigE drivers , at 15% utilization 2,469,496 bits as opposed to 1,000,000,000 bits capacity ?
Any assiatnce here would be gratefully appreciated from anyone who can identify why performance is slow
Cheers
Answers
- Is your question somehow ConfigMgr related?
- Proposed As Answer byJohn MarcumMVPWednesday, September 23, 2009 10:54 PM
- Marked As Answer byWallyMSFT, OwnerMonday, September 28, 2009 9:03 PM
All Replies
- Is your question somehow ConfigMgr related?
- Proposed As Answer byJohn MarcumMVPWednesday, September 23, 2009 10:54 PM
- Marked As Answer byWallyMSFT, OwnerMonday, September 28, 2009 9:03 PM
- My apologies Torsten if this is the wrong forum , yes ConfigMgr probrably is correct as I rearly need config advice here. I'll try re-posting if that helps ?
I'll await your response to see if this is appropriate
Cheers - Torsten is correct, this is the wrong forum you should post in the SQL forum but to answer one of your questions. "Does SQL by design grab all the memory, releasing to the operating system only when it comes under pressure? Memory from the taskmgr consistently fluctuates around 15-15.6 gig, leaving only a small portion for the OS" yes, by default SQL will grab all the RAM, there's a setting you need to change to lower that. Open SQL Management Studio, rightclick on the top level in the Object Explorer pane and go to properties then go to "memory"
John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum- Proposed As Answer byJohn MarcumMVPWednesday, September 23, 2009 10:54 PM
I think this is the right forum for performance-related questions for SQL: http://social.technet.microsoft.com/Forums/en-US/sqldatabaseengine/threads
Torsten and John are correct - we will always try to help where we can but your questions relate to how SQL Server works and not Configuration Manager, even though SQL Server is a dependency for Configuration Manager. You are more likely to get your question answered by experts in that field by posting to a SQL Server forum. Similarly, you should use the SQL Server documentation for information on how SQL works and how to configure it for best performance. The Configuration Manager documentation should cover anything SQL-related that is specific to Configuration Manager but for everything else, use the SQL Server resources.
- Carol
