?
Solved

MS SQL server consumes more memory and does not release the memory

Posted on 2014-03-19
4
Medium Priority
?
254 Views
Last Modified: 2014-03-20
Hi,
     I am running the database server with the following configuration.
The SQL Server consumes the hole memory(14 GB) and does not release the memory.
As a result the performance of the database server is reduced.

Please help me to resolve the issue.

 IBM System x3650
Windows 2008 server standard 64 bit
HDD:148 GB (RAID 5)
RAM :14 GB
MS SQL Server 2012 64 bit
Current Database Size: 7 GB
0
Comment
Question by:NARANTHIRAN
4 Comments
 
LVL 35

Assisted Solution

by:Dan Craciun
Dan Craciun earned 600 total points
ID: 39938963
Use this page to configure max server memory: http://technet.microsoft.com/en-us/library/ms178067.aspx

The easiest way is to use the Management Studio.

HTH,
Dan
0
 
LVL 52

Accepted Solution

by:
Carl Tawn earned 900 total points
ID: 39939159
You need to configure the MAX MEMORY to be at least a couple of GB less that the available system memory - you need to leave some for the OS to use.

Try running the following to bring the MAX MEMORY down to 12GB:
sp_configure 'show advanced options','1'
go

reconfigure with override
go

sp_configure 'max server memory (MB)','12288'
go

reconfigure with override
go

sp_configure 'show advanced options','0'
go

reconfigure with override
go

Open in new window

0
 
LVL 1

Expert Comment

by:SrinivasanITPro
ID: 39939318
Hi

I would check / change the following;

- Increase the Virtual Memory (Swap) to 1.5 times to RAM
- If any unused SQL Instances are available, I would STOP that.

Please check the above and feedback.

KS
0
 
LVL 75

Expert Comment

by:Anthony Perkins
ID: 39944116
The SQL Server consumes the hole memory(14 GB) and does not release the memory.
As a result the performance of the database server is reduced.

You have it back to front.  SQL Server by design will use all memory made available and not release it.  So if your performance is lousy it is not because SQL Server is using all the memory, quite the opposite, it just means that you either don't have enough memory or more likely you need to optimize the query or queries running.

Yes, you can set the max memory and provided you are not running anything else on that box i would recommend 11 or 12GB (see here)
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

An alternative to the "For XML" way of pivoting and concatenating result sets into strings, and an easy introduction to "common table expressions" (CTEs). Being someone who is always looking for alternatives to "work your data", I came across this …
One of the most important things in an application is the query performance. This article intends to give you good tips to improve the performance of your queries.
Via a live example combined with referencing Books Online, show some of the information that can be extracted from the Catalog Views in SQL Server.
Via a live example, show how to setup several different housekeeping processes for a SQL Server.
Suggested Courses

615 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question