Viewing 9 posts - 1 through 9 (of 9 total)
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...
August 4, 2008 at 7:29 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...
July 31, 2008 at 7:33 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...
July 31, 2008 at 7:23 am
Microsoft Windows Server 2003 Enterprise Edition Service Pack 1
July 30, 2008 at 8:37 am
I used procmon.exe to break down the individual threads of the exe. I didnt recognize anything strange but will admit it sure was alot of information. None of the developers...
July 30, 2008 at 8:35 am
Thank you. Links were very useful.
We had identified during the incident that the available memory in VAS was greatly diminished, and the available block size was much smaller than those...
July 30, 2008 at 8:28 am
Have run several traces. No working process seems to add up to the CPU cycles during the problem.
No external executeables appear in the Task Manager process list, only sqlsvr.exe as...
July 29, 2008 at 9:42 am
Enterprise Edition. AWE is enabled. 30 Gigs Max Memory 10 Gigs Min.
July 29, 2008 at 9:05 am
SQL 2005 Sp2 32bit on Server 2003 Sp1 4-way 36 Gigs of RAM.
already stated in post?
AWE enabled /3gb switch in boot.ini
July 29, 2008 at 8:09 am
Viewing 9 posts - 1 through 9 (of 9 total)