Tim, That doesn't seem excessive to me....whenever I'm looking at performance issues I turn on SQL and API logging at the server and run the ARLogAnalyzer against them...it tells me which processes are taking to long and I tweak that workflow, indexes, etc.
_____ From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Tim Rondeau Sent: Thursday, February 18, 2010 11:43 AM To: arslist@ARSLIST.ORG Subject: Performance issues ** Arsystem 7.1 patch 7 ITSM suite, using SLM, CMDB, Change Management, Problem and Incident We are running SQL 2005 on windows 2003 server, plenty of CPU/disk and RAM. Looking for some feed back on how some have handled performance issues. We process about 400 changes a day and about 800 incidents a day. Just seems like this system can't handle it. DB timeouts, white screens all the time. DBA of course states no issues. In March we are moving to Oracle RAC, which will be 2 robust db servers. APP will still be on windows. Thanks Tim _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
