New HW System Advice | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

New HW System Advice

Good day<br /><br />First of all please excuse my bad english, I’ll do my best! <img src=’/community/emoticons/emotion-5.gif’ alt=’;-)’ /><br /><br />Second I’ve been trough the forum reading every topic involving Raid, SAN and so… but honestly, too much information sometimes becomes disinformation, and I’m really puzzled at the moment.<br /><br />So, I’ll better go on with my quetion:<br /><br />We have a 50 Gb SQL 2000 database (growing 25% every year) from an ERP running actually on an IBM xSeries 235/4 Gb RAM/Raid 1 for system/Raid 5 for DBs/Windows 2000 Server/SQL Server 2k Enterprise SP4.<br /><br />We’ve been xperiencing performance problems in the last months, mostly with reads from OLAP applications, but also on batch writes with many inserts of processes done overnight or early in the morning. <br /><br />We have just bought a new Dell System composed of:<br /><br /><u><b>Del PowerEdge 2950</b></u><br />2 x Quad Core Xeon 2.66 Ghz<br />16 Gb RAM<br />2 x 76 Gb 15K disks (internals, mounted as a Raid 1)<br />Windows 2003 Enterprise Server<br /><br /><u><b>Dell/EMC PowerVault CX3-10 SAN Disk Raid Array</b></u><br />7 x 146 Gb 15K disks<br /><br />And we plan to migrate this DB to the new system, but as I’m a complete newbie in SAN I strongly need advice in the best option to configure for optimal performance.<br /><br />Which could be the typical/best Raid level for databases (and number of disk) for this DB?<br />Should I put the logs in the internal disks of the PowerEdge or move them to a Raid 1 in the SAN?<br />And the tempdb, could I store it on the internal disks?<br /><br />I would appreciate (if possible) direct/simple answer, but as maybe I dont give much insight for what I’m asking, I’ll be pleased to explain anything further.<br /><br />Thank you in advance and best regards.
While getting new hardware may help your performance issues, you may very well find out that it helps less than you think. This is because most SQL Server performance issues are related to poor application and T-SQL code, poor database design, poor indexing, and several other common mistakes. Be sure you learn how to identify poorly performing queries and how to "fix" them. In many cases, this is all that is needed, not new hardware, to fix performance issues. ——————————–
Brad M. McGehee, SQL Server MVP