SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

On the SQL server box. I bumped the RAM to 24 GB and allocated 20GB for SQL Server. Now the performance looks like attached print shot. I see there is barely 1 GB RAM available and only 31 Free. Is this normal? How does your perfmon looks like?

enter image description here

share|improve this question

closed as off-topic by RJ Cuthbertson, John Chapman, Benny Skogberg Nov 26 '13 at 7:01

  • This question does not appear to be about SharePoint within the scope defined in the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.

Is this a SharePoint question? – Dave Wise Nov 25 '13 at 21:08
This question appears to be off-topic because it is out of scope of this site as defined in the Help section. – RJ Cuthbertson Nov 25 '13 at 21:12
Yes. It is SharePoint question. I forgot to mention this db server dedicated to SharePoint. – Maria Burton Nov 25 '13 at 21:19
This question is off topic, since it's all about SQL Server. You are probably better off posting it on where they deal with Server specific questions. However, you need to clarify what your question is more specific, since it's a bit vague at the moment. – Benny Skogberg Nov 26 '13 at 7:01
But it is easily answered, in SQL Management Studio, login to your server, select the database server, right click and choose Properties. Under Memory -set a maximum limit of memory that gives the server enough slack to do normal server stuff. If this is not set, or equal to the amount of memory in the server, SQL will eat it all – Robert Lindgren Nov 26 '13 at 7:43

As the change in the allocation should not require a SQL restart I would guess that you have something else hogging the rest of the RAM. Look into the Proccesses tab and see if the culprit is visible there. As a best practice, nothing except SQL should be running there.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.