Q:

Why is SQL Server 2005 consuming so much memory (and it is not even running)

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?

A:

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.

A:

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.

