June 10, 2014 at 6:18 am
Guys please help!
ill explain the senario first,
-2 servers as active passive cluster
-64bg ram
-initial paging size set to 64 gb
-max paging size set to 90gb
Here
-the sql server is utilizing nearly 48gb of ram where max server memory is set to 50gb
-cannot reset the max server memory to a lesser value than 50gb in sql server
-the paging file usage is 99.9%
so
- i tried to increase the ram but the same issue persisits.
is there anything we can do about this?? please help!!
Regards,
Ashish George
June 10, 2014 at 6:23 am
.
June 11, 2014 at 12:08 pm
hmmm ... with an active passive cluster with 64 GB of RAM the largest paging file you should have configured is either 16 or possibly 32 GB. With 99% page file usage this begs the following question "Is this a 'dedicated' SQL Server ?". If the answer is no, then what are the characteristics of the memory required for the 'other' applications and/or services ?
Also, how are you determining the actual page file usage ? what tool are you using ?
The same applied to SQL Server memory usage as well.
As for setting the memory for SQL Server, why is 50 GB and issue since SQL Server is only using 48 GB ?
Have you tried to set the min/max SQL Server memory via sp_configure as opposed to using the SSMS GUI ?
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
June 12, 2014 at 12:08 am
Thanks for replying Rudy 🙂
See the server is dedicated for sql only, but an anti virus(symantic) is installed which is also utilizing memory like 38gb.
-i used perfmon to get the peak page file usage and the total and target sql server memory.
- one thing i did was, i made the initial and max vale for page file the same while monitering the peak usage using perfmon, the moment i set the initial=max=80gb the paging file usage came down drastically. dont know how!!!
-and i did not use sp_configure to set min/max SQL Server memory
i dont have a clue what happened! but setting the initial and max value the same resolved the excess paging file usage, and the memory utilization is also under control now.
what could have happened??!!
Regards,
Ashish George
June 12, 2014 at 7:51 am
is Semantec just scanning the SQL Server as an agent service or is it executing as an enterprise platform for a number of servers in your organization ?
if it is just an agent on the SQL Server this excessive paging may be due to the fact that there may not be the appropriate 'exclusions'. By that I mean it is trying to scan your .mdf, .ndf & .ldf files for all of the databases. Also, .bak and .trn files should be excluded as well.
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply