I have a Win 2003 Server set up with MS SQL Server 2008 R2 installed - together with a few other apps. When I start the server (it is running as a VM with VMWare), there are no performance problems at all. But as the day goes on, performance begins to suffer to the point that it might take 5 minutes just to open the Start Menu or close or minimize an open window. Everything just seems to grind to a halt.
I've taken a look at the processes tab in Task Manager, which also takes forever to open, and CPU Usage and Physical Memory appear fine. But the commit charge is very high .... it reports somewhere in the neighborhood of 8975 M / 9999 M. I don't really know what that means or if it's bad or good but I'm guessing it's bad.
I then took a look at the processes that were running and what their memory usage numbers were. One image - SQLSRVR.EXE - was reporting 5,800,000K (or thereabouts). That was, by far, the biggest consumer of memory. No other processes was reporting more that 500,000K and there were very few of them.
When I reboot the server, the memory usage for SQLSRVR.EXE is at about 495,000K. It just seems that once I begin to use the one database that's on the machine, that memory usage begins to climb and climb and climb and it never goes back down to a reasonable level unless I reboot.
When I use task manager and stop the SQLSRVR.EXE process, I am then unable to use SQL for anything but the machine starts to respond again - I can open and close windows, etc. without delay
I have 10 GB of memory allocated to the VM. That should be more than sufficient.
Any ideas about what the cause of the performance problems might be or how I might address them?