I'm helping a new member in Spanish forum. I never work with this hardware. May be I miss some information to ask. Opteron 2.2 Ghz, 4Gb RAM, windows 2003 sp1, sql 2000 sp4. /3G. After 2 days or sql start up (they have to reboot because performance) this are the numbers: Pages/sec: Average 1000, max 4000. Processor: average 97%. Avg. Disk queue length: 5. After reboot and for 2 days: Pages/sec: Max 120. Processor: 40% Avg. Disk Queue Length: 2 SQL server dedicated, Maintenance Jobs not optimal but reasonable. I suggest to run Profiler, reindex, etc. And, of course, talk with developers about long queries found with profiler. Anything else? Luis Martin Moderator SQL-Server-Performance.com All in Love is Fair Stevie Wonder All postings are provided “AS IS†with no warranties for accuracy.
i suggest neutering careless developers its too late to fix their methods but atleast they wont propagate after that, i would interested in knowing if CPU averages 40% is steady over a period of several days (normal hours) or does it creep up on pages/sec, ignore max, this should normally be zero, but you don't care about brief periods > zero
"after that, i would interested in knowing if CPU averages 40% is steady over a period of several days (normal hours) or does it creep up" After 1 or 2 days CPU grow up from 40% to 97% Thanks Joe. Luis Martin Moderator SQL-Server-Performance.com All in Love is Fair Stevie Wonder All postings are provided “AS IS†with no warranties for accuracy.
that would be a problem run profiler, and see which procs contribute the most growth in CPU these typically will have evil creatures, cursors, large intermediate results etc
Thanks, that's what I recommended to the guy. No new answer yet. Luis Martin Moderator SQL-Server-Performance.com All in Love is Fair Stevie Wonder All postings are provided “AS IS†with no warranties for accuracy.