GilaMonster (4/10/2014)
praneethydba (4/10/2014)
and he reduced the memory CAP to 10 GB, and no issues till now....Why? Why would you want more than half of the memory on the server to go completely to waste? Why would you want to cripple SQL by limiting its memory that much?
Sure, that's going to reduce the % memory used but it's counterproductive. Free memory is memory not being used, it's memory going to waste, it's a waste of money spent on that memory. By doing that you will have around 16GB memory doing absolutely nothing, may as well remove that 16GB from the server and throw it away as that's the equivalent of what's been done there.
What Gail said. Again. You do realise you're ignoring one of the best known and respected SQL Server experts on the planet. She's right, you're wrong, your client is wrong and the guy who did that is wrong. Seriously, listen to Gail and the others who have given you good advice. The reason your PLE is shocking is because you're ignored it.
I'm sorry for being so blunt, but what is the point of asking for advice if you're going to ignore it, even when it's explained to you? I just don't understand that. Admittedly I get it a lot. But I don't understand it.
I'm a DBA.
I'm not paid to solve problems. I'm paid to prevent them.