Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
txgeekgirl
Starting Member
18 Posts |
 Posted - 2012-10-04 : 15:30:53
|
| We are running a database that is 80GB on a new server (Win 2008 R2 DataCenter SP1) using SQL SERVER 2008 R2 SP2. We are throwing 8CPU, 64GB RAM, and have page filing set to server specs. Turned off Trusted Installer, have the buffer cache set to 14GB, and run about 200 users. We are experiencing massive RAM issues. Processes will show that SQL is using between 7-15 GB between 8am - 11PM but we are at a constant 50-57GB used. We are running a SQL Job to clean the buffer every 15 min. That does seem to help bring RAM down a bit. What else can we do? |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2012-10-04 : 17:00:06
|
| Why have you limited SQL to only 14GB of 64? I would set it up to about 56GB.-Chad |
 |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2012-10-04 : 17:00:51
|
| Assuming that this server is dedicated to SQL Server.-Chad |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
chadmat
The Chadinator
1974 Posts |
|
|
txgeekgirl
Starting Member
18 Posts |
Posted - 2012-10-05 : 00:06:06
|
| The SQL Server consistently needs between 7-14GB to run. Cleaning the cache lowered the RAM by 2-10GB per flush. What we found out was that having it on an overused Virtual Host was causing the issues. After moving it to a lesser used virtual host, the CPU usage went way down, the RAM went from 56-60 to 13-15 - we moved the SQL Server memory Max to 24GB, leaving the rest for user use. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2012-10-05 : 00:44:16
|
quote:
Originally posted by txgeekgirl
The SQL Server consistently needs between 7-14GB to run. Cleaning the cache lowered the RAM by 2-10GB per flush. What we found out was that having it on an overused Virtual Host was causing the issues. After moving it to a lesser used virtual host, the CPU usage went way down, the RAM went from 56-60 to 13-15 - we moved the SQL Server memory Max to 24GB, leaving the rest for user use.
SQL Server needs 7-14GB to run? What? That doesn't make any sense. Of course clearing the cache cleared out some memory, but that's not an efficient thing to do. The stuff was in memory for a reason. You are only causing performance problems by clearing out the cache regularly.Why are you setting the SQL Server memory so low? SQL Server is a memory hog. It's designed that way. Give it maybe 64-72GB if it is dedicated to SQL Server.I still don't understand what problem you are having, but you are definitely causing performance problems by doing these things.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
|
|
|
|
|
SQL Server Memory/Speed issues