July 31, 2008 at 7:23 am
No foreign dlls or clr procs identified with any of the sysinternals processor monitoring utilities. Day three after the bounce now and performance is beautiful. I have to think if any of the stored procedures, linked servers, or any other "normal application processes" were responsable, I wouldnt see such good performance for so many days after a bounce?
July 31, 2008 at 7:33 am
Day three after bounce all perf counters and monitoring looks normal.
Some great feedback here. My thanks to all.
Here is my best current theory......
a.)Known issues with using SQL2005 32bit with large amounts of memory.
b.)Windows Server at SP1, SP2 lists many memory related fixes (we are upgrading soon)
c.) Version (SQL Server 2005 - 9.00.3042.00) first release SP2 has known memory issues. (upgrade in process.)
These things coupled with recent volume expansions to the load reached a scaling threshold. *shrugs*
Paul D Ensor Sr.DBA
August 1, 2008 at 8:51 am
1) test and then upgrade to Cumulative Update 6 (or higher) to SP2 on sql server.
2) are you using lightspeed or another product to do backups?
3) run dbcc memorystatus and check the web for guidance on how to interpret output. Memtoleave is a possible culprit.
4) consider running dbcc freeproccache occassionally to see if that helps. Before running it check web for queries that will provide information about cached query plans.
5) hire a performance tuning consultant to get things addressed more quickly than back-and-forth forum posting will do. They can also mentor you to provide you with skills to address such issues going forward.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
August 4, 2008 at 7:29 am
We use hyperbac.
Doh!, I am the performance expert!
update...7 days now, performance is beautiful. It is possible that the 7 background traces I found and removed might have had more to do with the problem than I thought. I will update this post if it happens again.
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply