• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 652
  • Last Modified:

SQL Server Express 2012 process takes a lot of memory

I'm using SQL Server Express 2012 on Windows8. Looking at the memory usage of SQL Server Express service in Task Manager I see:
Before running SSMS: 10 MB.
During SSMS usage: 35 MB.
(Long) after closing SSMS: 154 MB! the process is stuck in memory, and remains like that until I end it manually or restart Windows.
Is this behaviour normal? Is there anyhing I can tune in SQL Server so that the process won't stuck in memory?
0
NNOAM1
Asked:
NNOAM1
  • 9
  • 6
1 Solution
 
EvilPostItCommented:
Are you referring to the memory usage for SSMS.exe or SQLServr.exe?

If SQLServr.exe, this is because when SQL Server uses memory it does not release it unless restarted.
0
 
NNOAM1Author Commented:
Not the SSMS itself, but the SQL service. Watch this picture - now it's gone up to 210 MB (don't mind the hebrew words and RTL task manager):my task manager right now
0
 
EvilPostItCommented:
In SSMS right click on the instance, goto the memory tab and change the max memory to 50mb. This should release a significant amount of memory. If you need to use more just change it back.
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
EvilPostItCommented:
Either that or just stop the SQL Server service when you are not using it...
0
 
NNOAM1Author Commented:
Is changing the max memory to 50mb going to reduce anything from the good function of SQL server? What are the consequences of such change?
0
 
EvilPostItCommented:
Yes, but if you change it back afterwards this is fine. It just allows you to release the used memory.
0
 
NNOAM1Author Commented:
I just did that and then closed SSMS. when i reopened SSMS I couldn't connent. The error message showed me the way to:
http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476
0
 
EvilPostItCommented:
You didnt need to close SSMS. If you stop and start the sql server service do you get the same error?
0
 
NNOAM1Author Commented:
YES.
0
 
EvilPostItCommented:
What if you just try to open a new query instead of using the Object Explorer section? Or maybe trying an osql connection from the command line?
0
 
EvilPostItCommented:
Also do you have any other services configured to use this SQL server? The other option might be to start it up in single user mode...
0
 
NNOAM1Author Commented:
A restart did the thing. Thanks anyway.
0
 
EvilPostItCommented:
Phew, thought I had broken your instance for a minute there... Probably best to raise the max memory a little though.

Did the reduction in max memory size have the desired result though?
0
 
NNOAM1Author Commented:
Even after the reduction the memory usage of the process remained high as in the beginning. I'll leave it like that.
0
 
EvilPostItCommented:
Unfortunately this is just how SQL Server operates. It is a service after all rather than a development tool like SSMS or Visual Studio.
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 9
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now