Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQL Memory settings Expand / Collapse
Author
Message
Posted Friday, March 14, 2014 1:39 PM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Monday, April 7, 2014 7:51 AM
Points: 86, Visits: 281
Hi,

I have SQL 2008 R2 installed on win2012 standard with 64 gig of ram. I have set sql to use 53 gig but task manager is only showing sqlserv using 32 gig? Any ideas?

Thanks
Post #1551334
Posted Saturday, March 15, 2014 5:47 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Saturday, March 15, 2014 10:42 PM
Points: 7, Visits: 21
It is depend on system file installation. if you have installed windows on 32-bit platform, SQL consume max 32 GB.
you have to install Windows and SQL server both on 64 bit platform.
i sure, it will help you.
Post #1551464
Posted Saturday, March 15, 2014 8:22 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 4:34 AM
Points: 40,618, Visits: 37,086
kshaileshbca (3/15/2014)
if you have installed windows on 32-bit platform, SQL consume max 32 GB.


You might want to check your facts....
The memory limit on 32 bit is, in fact 2GB by default. 3GB with the /3GB switch and well above 32 GB with the /PAE switch and AWE enabled



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1551481
Posted Saturday, March 15, 2014 8:25 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 4:34 AM
Points: 40,618, Visits: 37,086
TST, hard to say anything definitive without a lot more data, but if SQL doesn't need more than 32GB it won't necessarily allocate more.

Check that nothing else on the server is consuming a lot of memory. Make sure you don't have large pages enabled. If it's a VM, check what the reserved memory is for that guest.

Are there signs of memory pressure? Is SQL under any load?



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1551482
Posted Sunday, March 16, 2014 9:26 AM


Say Hey Kid

Say Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey Kid

Group: General Forum Members
Last Login: Yesterday @ 7:49 AM
Points: 680, Visits: 6,856
First thing I would look at is Windows able to see all the memory.
If Windows cannot see the 64GB, neither will SQL server.
Not all versions can see 64GB, and Numa architecture actual memory configuration can be a factor.
I had a 2 proc machine, we took one proc out for licensing, and needed to fill certain slots that the one proc could see.
You could override this in the BIOS, but not as efficient.

Then as Gail mentioned, SQL will not use the full allocation unless it needs to.
So you would have to check for signs of memory pressure.
Post #1551570
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse