Please start any new threads on our new site at We've got lots of great SQL Server experts to answer whatever question you can come up with.

Our new SQL Server Forums are live! Come on over! We've restricted the ability to create new threads on these forums.

SQL Server Forums
Profile | Active Topics | Members | Search | Forum FAQ
Save Password
Forgot your Password?

 All Forums
 SQL Server 2008 Forums
 SQL Server Administration (2008)
 SQL Memory
 Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

Constraint Violating Yak Guru

332 Posts

Posted - 05/13/2013 :  11:46:51  Show Profile  Reply with Quote
We have two similar reporting servers. Lets assume them Server A and Server B

On Server B, one of the ETL package SQL agent job is failed due an out of memory condition.
On both server Total RAM is 32 GB
Out of 32, 24 GB is allocated for SQL
Our monitoring tools say SQL is using 100% memory on server A
BUT SQL is using only 50% memory on Server B.

Both are identical servers. Why SQL is using only 50% of its allocated memory on Server B?
Do we need to reconfigure the memory on Server B? so that SQL can use 100% of its allocated memory.

8GB used by OS, So 8GB is not sufficiant for SSIS procedures? is this a memory leakage?


James K
Flowing Fount of Yak Knowledge

3873 Posts

Posted - 05/13/2013 :  13:10:57  Show Profile  Reply with Quote
That server A is using 100% of the allocated memory and B is using only 50% does not necessarily mean that there is anything wrong. SQL Server has its own OS (SQLOS) which manages its memory. As you run queries and more memory is required, SQL Server will grab more and more memory from the Windows OS, upto the maximum limit you specified. Once it has reached that max, it will not grab anymore from Windows OS, but it won't release the memory back to the Windows OS either.

So what may be happening in your situation is that Server A grabbed the maximum amount of memory it is available to because it needed that for some reason. Server B probably did not need to do that (yet) because of the nature of queries that were run against it.
Go to Top of Page

Posting Yak Master

160 Posts

Posted - 05/14/2013 :  03:13:08  Show Profile  Reply with Quote
In addition to James K response, it is also recommended to allocate 90% of RAM to Sql Server which is around 29GB as a best practice.
Go to Top of Page

Aged Yak Warrior

737 Posts

Posted - 05/15/2013 :  02:45:21  Show Profile  Send ahmeds08 a Yahoo! Message  Reply with Quote
You might run into memory issues if your Lookup transformation is set to Full cache.
Go to Top of Page
  Previous Topic Topic Next Topic  
 Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.02 seconds. Powered By: Snitz Forums 2000