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 123»»»

64-bit topped out at 4 GB used Expand / Collapse
Author
Message
Posted Thursday, August 12, 2010 1:11 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, May 2, 2014 8:21 AM
Points: 168, Visits: 423
I am moving databases to a dedicated server running:
Windows Server 2003 R2 Enterprise Edition 64-bit with 24 GB installed (all patches installed)
SQL Server 2005 Standard 64-bit SP3 (9.00.4053.00)

After a couple of days use SQL Server topped out at 4.1 GB, according to Task Manager. In trying to figure out why I’ve found that Windows Server 2005 R2 Enterprise Edition 64-bit supports 1 TB memory, and SQL Server 2005 Standard 64-bit should support up to 2 TB memory.

Any idea why we have struck a low ceiling? What parameter or setting is missing? I’ve been looking at TECHNET and MSDN and SQLServerCentral without much luck.



Post #968518
Posted Thursday, August 12, 2010 2:03 PM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: 2 days ago @ 8:02 AM
Points: 2,049, Visits: 3,596
Can you post the results of the following;


USE master;
GO
EXEC sp_configure 'show advanced option', '1';
RECONFIGURE;

EXEC sp_configure;


David

@SQLTentmaker
SQL Tentmaker
“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
Post #968548
Posted Friday, August 13, 2010 4:59 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 @ 6:44 AM
Points: 40,614, Visits: 37,079
Also
SELECT @@version



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 #968785
Posted Friday, August 13, 2010 5:28 AM


SSCrazy Eights

SSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy Eights

Group: General Forum Members
Last Login: Today @ 12:47 AM
Points: 9,928, Visits: 11,205
David,

This is a neat way of capturing that information:

select  name,
value,
value_in_use
from sys.configurations
where name in
(
N'min server memory (MB)',
N'max server memory (MB)',
N'awe enabled'
);

Looks like 32-bit SQL Server running under WOW64 to me.

Paul




Paul White
SQL Server MVP
SQLblog.com
@SQL_Kiwi
Post #968805
Posted Friday, August 13, 2010 6:37 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: 2 days ago @ 8:02 AM
Points: 2,049, Visits: 3,596
Paul White NZ (8/13/2010)
David,

This is a neat way of capturing that information:

select  name,
value,
value_in_use
from sys.configurations
where name in
(
N'min server memory (MB)',
N'max server memory (MB)',
N'awe enabled'
);

Looks like 32-bit SQL Server running under WOW64 to me.

Paul


Definitely like the view. Thanks!

Out of curiosity what makes you think this is a WOW configuration even though he stated that both Windows and SQL Server were 64-Bit?

As long as you are willing to share info, I'll take it in.


David

@SQLTentmaker
SQL Tentmaker
“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
Post #968856
Posted Friday, August 13, 2010 6:40 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 @ 6:44 AM
Points: 40,614, Visits: 37,079
David Benoit (8/13/2010)
Out of curiosity what makes you think this is a WOW configuration even though he stated that both Windows and SQL Server were 64-Bit?


4GB is the maximum amount of memory a 32 bit app can use running on a 64 bit OS.



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 #968858
Posted Friday, August 13, 2010 6:43 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: 2 days ago @ 8:02 AM
Points: 2,049, Visits: 3,596
GilaMonster (8/13/2010)

4GB is the maximum amount of memory a 32 bit app can use running on a 64 bit OS.


Thanks Gail. Hate to think that this is what they did but I can see where you would come to that conclusion.


David

@SQLTentmaker
SQL Tentmaker
“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
Post #968862
Posted Friday, August 13, 2010 6:46 AM


SSCrazy Eights

SSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy Eights

Group: General Forum Members
Last Login: Today @ 12:47 AM
Points: 9,928, Visits: 11,205
David Benoit (8/13/2010)
Out of curiosity what makes you think this is a WOW configuration even though he stated that both Windows and SQL Server were 64-Bit?

SQL Server x86 gets a 4GB virtual address space when running under WOW:
http://blogs.msdn.com/b/slavao/archive/2006/03/12/550096.aspx

None of the alternative configurations I can think of would produce the memory usage reported by Task Manager (AWE requires locked pages, and non-paged memory isn't reported in TM usage).

Paul




Paul White
SQL Server MVP
SQLblog.com
@SQL_Kiwi
Post #968865
Posted Friday, August 13, 2010 6:56 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 @ 6:44 AM
Points: 40,614, Visits: 37,079
David Benoit (8/13/2010)
GilaMonster (8/13/2010)

4GB is the maximum amount of memory a 32 bit app can use running on a 64 bit OS.


Thanks Gail. Hate to think that this is what they did but I can see where you would come to that conclusion.


I had a recent situation with a client of mine, they told me they were running SQL 2005 x64. I was doing a perf tuning exercise and, from the data I had it was clear that SQL needed more memory. I checked perfmon and SQL was using 4GB out of 16 GB. I checked the SQL error log. Right at the top:

Microsoft SQL Server 2005 - 9.00.3042 (X86)

Person who had installed SQL had installed the 32 bit instead of 64 bit, and no one had checked.



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 #968869
Posted Friday, August 13, 2010 6:59 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: 2 days ago @ 8:02 AM
Points: 2,049, Visits: 3,596
Thanks Paul and Gail. Definitely great observations. Not sure if the OP is even following the thread but I certainly appreciate it.

David

@SQLTentmaker
SQL Tentmaker
“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
Post #968871
« Prev Topic | Next Topic »

Add to briefcase 123»»»

Permissions Expand / Collapse