I have a client running Server 2003 SBS 32-bit. 4GB RAM, full GB Ethernet throughout the backbone and other connected equiptment, Xeon E5410 2.33Ghz. This server is hosting 2 SQL Databases - SQL Server 2005, The Centrally Managed AV, DNS, DHCP, AD, VPN, Remote Web Workplace(not in use but turned on). There are about 12 concurrent users in the environment. The AV is Trend Micro WFBS Standard. URL Scanning is turned off and all the Microsoft Server services are listed as exclusions as per Trend Micro Support. Backups are performed with Storagecraft ShadowProtect nightly after hours.
Now that that's out of the way...
The users that utilize one of the databases for their application frequently have "not responding" errors on their computers. We installed a piece of monitoring software and it found some IIS errors that we resolved, as well as some DNS errors that we also resolved. So far it has thrown nothing back at us other than a possible Disk error that we have looked into and determined it was a fake, or accidentally tripped, alert.
The SQL service is currently using 1.4GB of RAM and has 1,000,000 page faults. The system is up to 778,013,197 Page Faults. I rebooted this server exactly 1 week ago today. Plenty of page faults from other applications suce as SVCHOST, NTFRS and explorer.exe.
I can't figure out what might be causing these users to get the not responding errors from the DB application. Should I be worried about the Page Faults? I can't upgrade the RAM but we have discussed replacing the server. CPU usage is most of the time 99% System Idle Process, which i know is safe. Network utilization is not abnormal.
Is there a way I can limit the SQL Servers memory? 1.4GB seems like a lot for their databases. the first DB is accessed by 5-6 users at any given time, give or take a user, and the second DB is limited to 2 concurrent users at any given time.
Any help is appreciated, I hope i provided enough backround info.