?
Solved

SQL Server only using 1.7GB of available RAM

Posted on 2011-03-01
4
Medium Priority
?
839 Views
Last Modified: 2012-05-11
We have a Windows 2008 32 bit Enterprise Edition server that has 8GB of RAM installed. The server is running SQL Server 2008 32 bit Enterprise Edition, but SQL is using no more than 1.7GB of RAM. We have using the AWE command is SQL Server but the SQL only used 60MB once this command had been run. We would like to configure SQL to use all of the RAM available for use on the server.

Does anyone have any ideas how to configure SQL Server 2008 to utilise all RAM available
0
Comment
Question by:MartynLawson
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
4 Comments
 
LVL 5

Accepted Solution

by:
sindhuxyz earned 750 total points
ID: 35006259
0
 
LVL 1

Author Comment

by:MartynLawson
ID: 35007110
I've looked through the articles that you have sent through and we have already performed the tasks that you have suggested.

When the server was first built it was only registering 3.34GB in Task Manager, so we ran bcdedit /set PAE forceenable and all the RAM became visible, but SQL was only showing as using 1.7GB. We then tried to configure AWE, but once this had been configured it showed in Task Manager that it was only accessing 60MB. I have been led to believe that this is not correct, but at the some time the SQL process is maxing out the CPU when performing any transactions.

Do you have any other suggestions for correcting the fault that we are experiencing?
0
 
LVL 40

Assisted Solution

by:lcohan
lcohan earned 750 total points
ID: 35030509
After you enable AWE you should check in Control Panel under Security  - Local Policy and make sure  "Lock Pages in Memory" is enabled for the account starting SQL Server Service. Please see details at:  http://msdn.microsoft.com/en-us/library/ms179301.aspx
0
 
LVL 1

Author Closing Comment

by:MartynLawson
ID: 35084383
These solutions did help towards the resolution of the problem. The utilisation in task manager does not appear to be a true representation of the memory allocated to the SQL server. We maanged to find the true information when looking through perfmon

Thanks very much
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

Question has a verified solution.

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

For anyone that has accidentally used newSID with Server 2008 R2 (like I did) and hasn't been able to get the server running again because you were unlucky (as I was) and had no backups - I was able to get things working by doing a Registry Hive rec…
After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
This tutorial will show how to push an installation of Backup Exec to an additional server in both 2012 and 2014 versions of the software. Click on the Backup Exec button in the upper left corner. From here, select Installation and Licensing, then I…
To efficiently enable the rotation of USB drives for backups, storage pools need to be created. This way no matter which USB drive is installed, the backups will successfully write without any administrative intervention. Multiple USB devices need t…

719 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