Server Fault is a question and answer site for system and network administrators. 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

Lately, I have noticed that SQL Server is consuming too much memory even though the Management Studio is not running. It consumes as much as 500,000K of memory. I understand that the SQL Server instance has to run but with this much memory?

Is there anything I can do to fix this?

alt text

share|improve this question

migrated from Jun 23 '10 at 19:42

This question came from our site for professional and enthusiast programmers.

up vote 10 down vote accepted

The SQL Server IS running - whether or not you have Management Studio have open. SQL Server will use as much memory as it needs and can get - by default - you can change that, if you want to limit SQL Server to a certain amount of RAM. But be aware: SQL Server needs a good chunk of RAM to work properly - if you restrict it too much, it'll slow down considerably.

share|improve this answer

SQL Server will use as much memory as it needs. You don't have to be running SSMS for it to use memory - you have things like the data cache which will cache data in memory when queried to make it faster to retrieve for subsequent calls. Any connections being made to the db server will use memory. It shouldn't be anything to worry about, if the OS needs more memory for other tasks, SQL Server can release it. But if there's no pressure for memory, then SQL Server will use as much as it can.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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