Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / DB Engine / SQL Server / March 2008

Tip: Looking for answers? Try searching our database.

Enterprise Manager reporting wrong OS memory (SQL 2000 SP4+)

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Ed Enstrom - 04 Mar 2008 04:14 GMT
I have a SQL Server 2000 instance on a Windows Server 2003 cluster.  The SQL Server instance is at SP4 with the
additional hot fix for the AWE memory problem.

We updated the OS memory from 4 GB to 8 GB but Enterprise Manager is still showing only 4 GB of RAM.  Task Manager on
the server itself shows all 8 GB.

The /PAE switch is in boot.ini (not /3GB switch) and AWE is turned on.  The startup log says AWE is enabled.

Still, EM shows only 4 GB of RAM.  I have another instance on a non-clustered machine and it shows all 8 GB correctly.

Any ideas what the problem could be?

Thanks,
Ed
Uri Dimant - 04 Mar 2008 08:00 GMT
Ed
Did  you set up MAX Memory?

>I have a SQL Server 2000 instance on a Windows Server 2003 cluster.  The
>SQL Server instance is at SP4 with the additional hot fix for the AWE
[quoted text clipped - 14 lines]
> Thanks,
> Ed
Ed - 04 Mar 2008 14:49 GMT
Hi Uri,

Yes, max memory is set.  Here is ooutput of sp_configure for memory options:

name            minimum    maximum        config_value    run_value
awe enabled        0    1        1        1
max server memory (MB)    4    2147483647    6144        6144
min server memory (MB)    0    2147483647    0        0

> Ed
> Did  you set up MAX Memory?
Andrew J. Kelly - 04 Mar 2008 14:50 GMT
Where exactly are you seeing this 4GB?   What does sp_configure show for the
MAX Memory?

Signature

Andrew J. Kelly    SQL MVP
Solid Quality Mentors

>I have a SQL Server 2000 instance on a Windows Server 2003 cluster.  The
>SQL Server instance is at SP4 with the additional hot fix for the AWE
[quoted text clipped - 14 lines]
> Thanks,
> Ed
Ed - 04 Mar 2008 15:34 GMT
In Enterprise Manager, right-click on the instance.
On the General tab, the OS Memory: line shows 3839(MB)
The Memory tab shows range of 0 to 3839 MB.
in sp_configure, max server memory (MB) is 6144

> Where exactly are you seeing this 4GB?   What does sp_configure show for the
> MAX Memory?
Andrew J. Kelly - 04 Mar 2008 16:31 GMT
It sounds like either the hotfix did not succeed or you applied the wrong
one. If you run xp_msver do you see the proper version for that hotfix?  Is
this Enterprise Edition of SQL Server?  This was on a cluster. Did the
hotfix get applied to both nodes?

Signature

Andrew J. Kelly    SQL MVP
Solid Quality Mentors

> In Enterprise Manager, right-click on the instance.
> On the General tab, the OS Memory: line shows 3839(MB)
[quoted text clipped - 4 lines]
>> the
>> MAX Memory?
Ed - 04 Mar 2008 17:04 GMT
Hi Andrew,

Results from xp_msver:
Index    Name    Internal_Value    Character_Value
1    ProductName        Microsoft SQL Server
2    ProductVersion    524288    8.00.2187
3    Language    1033    English (United States)
4    Platform        NT INTEL X86
5    Comments        NT INTEL X86
6    CompanyName        Microsoft Corporation
7    FileDescription        SQL Server Windows NT
8    FileVersion        2000.080.2187.00
9    InternalName        SQLSERVR
10    LegalCopyright        © 1988-2004 Microsoft Corp. All rights reserved.
11    LegalTrademarks        Microsoft® is a registered trademark of Microsoft
Corporation. Windows(TM) is a trademark of Microsoft Corporation
12    OriginalFilename        SQLSERVR.EXE
13    PrivateBuild       
14    SpecialBuild    143327232   
15    WindowsVersion    248381957    5.2 (3790)
16    ProcessorCount    4    4
17    ProcessorActiveMask    15    0000000f
18    ProcessorType    586    PROCESSOR_INTEL_PENTIUM
19    PhysicalMemory    3839    3839 (4025999360)
20    Product ID       

The hotfix was applied.  So far as I know, it was successful (no errors).  
It is on both nodes of the cluster.  Windows Server 2003 Enterprise (need
this version for clustering).

This is what is driving me nuts.  Everything looks right, but SQL Server is
not seeing all the memory.

> It sounds like either the hotfix did not succeed or you applied the wrong
> one. If you run xp_msver do you see the proper version for that hotfix?  Is
[quoted text clipped - 9 lines]
> >> the
> >> MAX Memory?
Andrew J. Kelly - 04 Mar 2008 21:44 GMT
OK well you actually have the Cumulative Update not just the hotfix but it
still should contain it as far as I know. What do the perfmon counters for
SQL Memory Target and Total memory show?  If they show the 6GB then it
sounds like a bug in the gui.  You may need to contact PSS if perfmon or
DBCC MEMORYSTATUS are not showing the right amount.

Signature

Andrew J. Kelly    SQL MVP
Solid Quality Mentors

> Hi Andrew,
>
[quoted text clipped - 45 lines]
>> >> the
>> >> MAX Memory?
Ed - 05 Mar 2008 16:25 GMT
Andrew,

Perfmon shows 3.2 GB total memory for SQL Server, so the problem is not a UI
issue.  I have another server (non-clustered) at the same SQL 8,00.2187 (SP4)
version with 8 GB and it is working properly.  I suspect the problem is
related to clustering, but I do not know enough about that to pinpoint the
cause.  I will continue to investigate.

Thanks for the DBCC MEMORYSTATUS idea.  I did not know about this function.  
It does not appear in Help.

Ed

> OK well you actually have the Cumulative Update not just the hotfix but it
> still should contain it as far as I know. What do the perfmon counters for
> SQL Memory Target and Total memory show?  If they show the 6GB then it
> sounds like a bug in the gui.  You may need to contact PSS if perfmon or
> DBCC MEMORYSTATUS are not showing the right amount.
Andrew J. Kelly - 05 Mar 2008 17:15 GMT
It certainly sounds like the Hoxfix didn't work properly. I would give MS a
call.

Signature

Andrew J. Kelly    SQL MVP
Solid Quality Mentors

> Andrew,
>
[quoted text clipped - 19 lines]
>> sounds like a bug in the gui.  You may need to contact PSS if perfmon or
>> DBCC MEMORYSTATUS are not showing the right amount.
Ed - 05 Mar 2008 17:53 GMT
Right.  I've pretty much come to the same conclusion.

Thanks for the help.

Ed

> It certainly sounds like the Hoxfix didn't work properly. I would give MS a
> call.
Ed - 08 Mar 2008 15:32 GMT
The problem has been solved.  It turns out that we had to stop and restart
the cluster in order for SQL Server to see the extra memory.  We had to wait
until Friday night to do it.

When we added the memory, we failed over the SQL Server service, took the
machine down, added the memory and brought the machine back up again.  The
cluster was never stopped.

Thanks again for your help.

Ed

> It certainly sounds like the Hoxfix didn't work properly. I would give MS a
> call.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.