May 8, 2009 at 4:59 am
Inherited (aka dumped on my desk) a "business critical" database which is suffering from performance problems :doze: . Looking into the underlying design :unsure: leaves a little to be desired and I'm working on that (missing PKs, FKs, use of :sick: ntext).
Meanwhile I'm wondering if a log drive (E:) would help :ermm: . Or more RAM :ermm: . Or anything really with the CPU running at an average of 75%+ and 700 user processes it's not really coping.
Version: SQL 2005 standard
CPU: Dual Xeon 2.66Ghz
RAM: 3Gb
C: RAID 1
D: RAID 5
May 8, 2009 at 9:11 am
Are you seeing IO bottlenecks? (perfmon, physical disk:avg sec/read, physical disk:avg sec/write, physical disk:% idle time)
First things first, before you go looking for hardware. Fix the queries, fix the indexes. If you can tune the queries and create indexes that will support those queries you will see a much greater performance improvement than if you bought new hardware.
If you haven't a clue where to start, suggest to the boss that getting a consultant in (someone who specialised in performance tuning), is likely to get things fixed far quicker than you could, and you'll learn from them in the process.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply