SQL Server Performance Forum – Threads Archive

Slow performance for SQL Server 2000 on IBM x366

Hi all, I am facing a problem with SQL Server 2000 on Windows 2003 Server, Here’s the environment details: Server hardware IBM xSeries x366 wiht x3 architecturehttp://www-03.ibm.com/servers/eserver/xseries/x366/specs.html
Dual Xeon 3.7 processors
4 GB of RAM
2 x 73 GB SAS Internal Hard Disks Server Software Microsoft Windows Server 2003 R2 (32 bit)
Microsoft SQL Server 2000 Standard Edition SP4 (Standard Configuration). (32 bit) Problem Description We are facing slow performance regarding any operations that require write access to SQL Server ( visible when we do backup and restore from business application [ Restore takes too much time ]). Testing sqlio tool http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlIObasics.mspx#EXNAE ) from Microsoft, we found that our Laptop outperform IBM server by 7 times !!!!!! Reinstalling SQL with empty databases to avoid data and ugly written queries leads to the same results. The same software settings on a regular PC performs much more better that IBM server. No hardware errors is reported neither Windows errors.
What possibly could be the reason for such slowness in SQL write operations ?

I refer and following thishttp://sqljunkies.com/Article/D1B7C756-4725-4D31-A53D-C0A47976E6BB.scuk whenever I get performance issues, a good one to tackle the issues. KBAs also help
http://support.microsoft.com/kb/224587/
http://support.microsoft.com/kb/243589/ Satya SKJ
Microsoft SQL Server MVP
Contributing Editor & Forums Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing.

Thanks Satya, I made some benchmark tests on the server itself. It looks like we have a bottleneck in write operations on system. I checked hardware manager, check the disk drives and found that write cache is disabled. Upon enabling it , performance boosted like it should be <img src=’/community/emoticons/emotion-1.gif’ alt=’

‘ /> Thanks for you r help, Maged Hussein

Make sure you have a cache with battery backup on your raid controller before enabling write cache.

]]>