I need some help as far as arguments of ideas to combat an issue. I recently started a new position and one of the divisions I support has some of what I consider sub-standard SQL Server 2005 configurations. The volume of connections is 300-500 users at any given time on 8G of RAM 4 Processor machines in a 2-box cluster setup. For some reason they've set the swap file to 2G. I always in past positions had the swap file configured to 2xRAM. The symptoms I'm seeing are very slow processing at peak times when memory is maxed out. I'm trying to convince the Intel and Application DBAs that I believe their chief problem is the AWE configured to max and swap files too small. Can someone point me to some solid document I can point them to to back up what I'm saying. As a new DBA, I need this as I don't have the track record with them for them to take what I say at face value. Or if you have other ideas, I'd appreciate those too. These are tax systems that users access via the internet. I think they have some bad code causing some blocking too. I think they also need to break up their data files across multiple filegroups to increase performance as well. Ideas on the best things to attack first?

Cathy, Since just the Exchange geeks hang out here you might want to re-post this ina suitable SQL forum over here: http://forums.microsoft.com/TechNet/default.aspx?ForumGroupID=93&SiteID=17