Hi all I am looking at a SQL 2000 std server running on windows 2000 std. The box is a quad HTT with 4gb ram. H/W Raid 10 across 4 disks, with a separate page file disk. SQL is now configured to use all 4 processors (it was only using 3 until 30 mins ago!!) and to use a fixed amount of 2gb ram. The application uses 4 DB's two of which are 9gb in size the other 2 are tiny. The system is performing slow and processor usage is bouncing between 50-100, i would say an avg of 70%. My hunch is that it needs more ram for SQL therefore I am thinking 2003 std or 2000 adv (with /3gb) and sql 2000 ent (the app is not certified for sql 2005 yet). Then allocated 3 gb to SQL from the 4gb on the box, or maybe even up the ram to 8gb. What is the best way to determine wither SQL requires more ram as the server OS itself does not. I have just switched SQL to use dynamic from 0-2GB to see what it tries to use. I have looked at; Disk queue and although there are spikes avr across 8 hrs was 1.6. Server work queue is also below 2. %read and % write time, but didn#%92t really know how to interoperate. And from some reading up seem to provide poor statistics for this?? Memory pages/sec below 1. So I guess I am asking how best to tell if SQL in this setup requires more than 2gb and therefore an OS and SQL version upgrade? And if anyone has any suggestions on where best to look next. Cheers Stuart.