Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
david32
Starting Member
15 Posts |
Posted - 2008-08-21 : 22:09:03
|
| Hi Folks,I seem to be having paging problems after installing several instances on my sql server. I hope I am giving enough info to get some good advice cos I'm stumped.I am working off a dual quad core processor (2.4ghz) with 16 GB. there are 10 instances on this machine but only 4 get any serious use at present. The other 6 are just got maintenance plans for checkdb, backup, index defrag and db shrink at night.When I got in this morning Operations Manager sent me an alert that Committed Bytes in use was too high. It was above 80% and the page file was 16GBThe instances I have installed have all the services - but some have been disabled. Disabled are: reporting services only 3 installed have full text searchWith max memory server option the total max memory for all instance is 14.5 GB. This is a dedicated SQL serverAnyway I knew previously that this was a problem so I did some memory logging last night - with the following countersMemory - % committed bytes in useMemory - % Avialable bytesPhysical disk - Disk time (total)Process - Page File Bytes (for each sql instance) After some more investigation I noticed a increase in %committed %disk time and page file bytes (for particular instances) when the maintenance plan was kicking in (as referred earlier) - in particular the checkdb was happening. The thing I don't understand is even though there was an increase in paging there was still several GB of avialable memory. This is one entry when there was a sharp increase of committed bytesTime: "23:54:51.642",Committed in use % :"60.5310425495163",Memory Avialable:"7125131264",Disk Time :"792.23080722099905",Page File Bytes (for problem instance at this point): 1265430528 was (280400000 15 seconds before)Has anyone got any advice help for me? |
|
|
|
|
|