Hi, please let me know if I enable AWE and PAE and turn on /3 GB switch, why
can't I see sqlserver.exe or total/target server memory more that 2.72 GB?
Event though there is a page/sec goes upto 6000. Server must need memory more
than 3 GB. My email address is : atiqur_rahman02@.yahoo.com or you can paste
here. Thanks for your help!
How much memory does your server machine have? What is the version and
edition of the operating system and SQL Server you are using?
Anith
Showing posts with label target. Show all posts
Showing posts with label target. Show all posts
Wednesday, March 7, 2012
AWE and Target Server Memory
Prior to enabling AWE, we had 8GB RAM but utilizing only 2.7GB.
This is the script we used to enable AWE and set Max Memory, essentially
leaving 2GB for the OS.
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
Just so you are aware, we do have the boot.ini with the PAE and 3GB switches
set.
The question I have, is what I am seeing for Target and Total Server Memory:
Target Server Memory(KB) = 4087767
Total Server Memory(KB) = 4087747
I was expecting to see more Target Server Memory being used (closer to 6GB)
rather than only 4087767KB / 3.898GB.
Please explain.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200609/1What version of SQL Server are you using?
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
.
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:663faf808d6ce@.uwe...
Prior to enabling AWE, we had 8GB RAM but utilizing only 2.7GB.
This is the script we used to enable AWE and set Max Memory, essentially
leaving 2GB for the OS.
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
Just so you are aware, we do have the boot.ini with the PAE and 3GB switches
set.
The question I have, is what I am seeing for Target and Total Server Memory:
Target Server Memory(KB) = 4087767
Total Server Memory(KB) = 4087747
I was expecting to see more Target Server Memory being used (closer to 6GB)
rather than only 4087767KB / 3.898GB.
Please explain.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200609/1|||SQL 2000
Tom Moreau wrote:
>What version of SQL Server are you using?
>Prior to enabling AWE, we had 8GB RAM but utilizing only 2.7GB.
>This is the script we used to enable AWE and set Max Memory, essentially
>leaving 2GB for the OS.
>sp_configure 'show advanced options', 1
>RECONFIGURE
>GO
>sp_configure 'awe enabled', 1
>RECONFIGURE
>GO
>sp_configure 'max server memory', 6144
>RECONFIGURE
>GO
>Just so you are aware, we do have the boot.ini with the PAE and 3GB switche
s
>set.
>The question I have, is what I am seeing for Target and Total Server Memory
:
>Target Server Memory(KB) = 4087767
>Total Server Memory(KB) = 4087747
>I was expecting to see more Target Server Memory being used (closer to 6GB)
>rather than only 4087767KB / 3.898GB.
>Please explain.
Message posted via http://www.droptable.com|||Which SP level? What's the result of running:
SELECT @.@.VERSION
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
.
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:663fdb867f662@.uwe...
SQL 2000
Tom Moreau wrote:
>What version of SQL Server are you using?
>Prior to enabling AWE, we had 8GB RAM but utilizing only 2.7GB.
>This is the script we used to enable AWE and set Max Memory, essentially
>leaving 2GB for the OS.
>sp_configure 'show advanced options', 1
>RECONFIGURE
>GO
>sp_configure 'awe enabled', 1
>RECONFIGURE
>GO
>sp_configure 'max server memory', 6144
>RECONFIGURE
>GO
>Just so you are aware, we do have the boot.ini with the PAE and 3GB
>switches
>set.
>The question I have, is what I am seeing for Target and Total Server
>Memory:
>Target Server Memory(KB) = 4087767
>Total Server Memory(KB) = 4087747
>I was expecting to see more Target Server Memory being used (closer to 6GB)
>rather than only 4087767KB / 3.898GB.
>Please explain.
Message posted via http://www.droptable.com|||Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows
NT 5.2 (Build 3790: Service Pack 1)
Tom Moreau wrote:[vbcol=seagreen]
>Which SP level? What's the result of running:
>SELECT @.@.VERSION
>SQL 2000
>Tom Moreau wrote:
>[quoted text clipped - 27 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200609/1|||What happens if you set the min server memory and restart SQL Server?
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
.
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:664097d00a0ed@.uwe...
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows
NT 5.2 (Build 3790: Service Pack 1)
Tom Moreau wrote:[vbcol=seagreen]
>Which SP level? What's the result of running:
>SELECT @.@.VERSION
>SQL 2000
>Tom Moreau wrote:
>[quoted text clipped - 27 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200609/1|||I am away from the office and will not have access to the server until
tomorrow around 10:00 MST. Even then we will not be able to restart the
service until late tomorrow evening. Do you have a theory about setting "min
server memory"? I believe I recall on the "max server memory" the minimum is
set to 4. Anyway, just trying to follow your thought process on why the "min
server memory" might be inhibiting memory use.
Tom Moreau wrote:[vbcol=seagreen]
>What happens if you set the min server memory and restart SQL Server?
>Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
>Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Window
s
>NT 5.2 (Build 3790: Service Pack 1)
>Tom Moreau wrote:
>[quoted text clipped - 7 lines]
Message posted via http://www.droptable.com|||In SQL 2005, server memory will gradually climb to the max server memory,
whether or not you're using AWE. In SQL 2000, it's supposed to take it in
one chunk, IIRC. I'm thinking that if max = min = whatever you really want,
then you may be forcing it up to that level straight away.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
.
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:6641520a8602d@.uwe...
I am away from the office and will not have access to the server until
tomorrow around 10:00 MST. Even then we will not be able to restart the
service until late tomorrow evening. Do you have a theory about setting "min
server memory"? I believe I recall on the "max server memory" the minimum is
set to 4. Anyway, just trying to follow your thought process on why the "min
server memory" might be inhibiting memory use.
Tom Moreau wrote:[vbcol=seagreen]
>What happens if you set the min server memory and restart SQL Server?
>Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
>Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on
>Windows
>NT 5.2 (Build 3790: Service Pack 1)
>Tom Moreau wrote:
>[quoted text clipped - 7 lines]
Message posted via http://www.droptable.com|||This is the 'expected behavior' of 8.00.2039 and is fixed in 8.00.2040. See
http://support.microsoft.com/defaul...kb;en-us;899761
Linchi
"cbrichards via droptable.com" wrote:
> Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
> Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windo
ws
> NT 5.2 (Build 3790: Service Pack 1)
>
> Tom Moreau wrote:
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200609/1
>
This is the script we used to enable AWE and set Max Memory, essentially
leaving 2GB for the OS.
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
Just so you are aware, we do have the boot.ini with the PAE and 3GB switches
set.
The question I have, is what I am seeing for Target and Total Server Memory:
Target Server Memory(KB) = 4087767
Total Server Memory(KB) = 4087747
I was expecting to see more Target Server Memory being used (closer to 6GB)
rather than only 4087767KB / 3.898GB.
Please explain.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200609/1What version of SQL Server are you using?
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
.
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:663faf808d6ce@.uwe...
Prior to enabling AWE, we had 8GB RAM but utilizing only 2.7GB.
This is the script we used to enable AWE and set Max Memory, essentially
leaving 2GB for the OS.
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
Just so you are aware, we do have the boot.ini with the PAE and 3GB switches
set.
The question I have, is what I am seeing for Target and Total Server Memory:
Target Server Memory(KB) = 4087767
Total Server Memory(KB) = 4087747
I was expecting to see more Target Server Memory being used (closer to 6GB)
rather than only 4087767KB / 3.898GB.
Please explain.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200609/1|||SQL 2000
Tom Moreau wrote:
>What version of SQL Server are you using?
>Prior to enabling AWE, we had 8GB RAM but utilizing only 2.7GB.
>This is the script we used to enable AWE and set Max Memory, essentially
>leaving 2GB for the OS.
>sp_configure 'show advanced options', 1
>RECONFIGURE
>GO
>sp_configure 'awe enabled', 1
>RECONFIGURE
>GO
>sp_configure 'max server memory', 6144
>RECONFIGURE
>GO
>Just so you are aware, we do have the boot.ini with the PAE and 3GB switche
s
>set.
>The question I have, is what I am seeing for Target and Total Server Memory
:
>Target Server Memory(KB) = 4087767
>Total Server Memory(KB) = 4087747
>I was expecting to see more Target Server Memory being used (closer to 6GB)
>rather than only 4087767KB / 3.898GB.
>Please explain.
Message posted via http://www.droptable.com|||Which SP level? What's the result of running:
SELECT @.@.VERSION
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
.
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:663fdb867f662@.uwe...
SQL 2000
Tom Moreau wrote:
>What version of SQL Server are you using?
>Prior to enabling AWE, we had 8GB RAM but utilizing only 2.7GB.
>This is the script we used to enable AWE and set Max Memory, essentially
>leaving 2GB for the OS.
>sp_configure 'show advanced options', 1
>RECONFIGURE
>GO
>sp_configure 'awe enabled', 1
>RECONFIGURE
>GO
>sp_configure 'max server memory', 6144
>RECONFIGURE
>GO
>Just so you are aware, we do have the boot.ini with the PAE and 3GB
>switches
>set.
>The question I have, is what I am seeing for Target and Total Server
>Memory:
>Target Server Memory(KB) = 4087767
>Total Server Memory(KB) = 4087747
>I was expecting to see more Target Server Memory being used (closer to 6GB)
>rather than only 4087767KB / 3.898GB.
>Please explain.
Message posted via http://www.droptable.com|||Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows
NT 5.2 (Build 3790: Service Pack 1)
Tom Moreau wrote:[vbcol=seagreen]
>Which SP level? What's the result of running:
>SELECT @.@.VERSION
>SQL 2000
>Tom Moreau wrote:
>[quoted text clipped - 27 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200609/1|||What happens if you set the min server memory and restart SQL Server?
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
.
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:664097d00a0ed@.uwe...
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows
NT 5.2 (Build 3790: Service Pack 1)
Tom Moreau wrote:[vbcol=seagreen]
>Which SP level? What's the result of running:
>SELECT @.@.VERSION
>SQL 2000
>Tom Moreau wrote:
>[quoted text clipped - 27 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200609/1|||I am away from the office and will not have access to the server until
tomorrow around 10:00 MST. Even then we will not be able to restart the
service until late tomorrow evening. Do you have a theory about setting "min
server memory"? I believe I recall on the "max server memory" the minimum is
set to 4. Anyway, just trying to follow your thought process on why the "min
server memory" might be inhibiting memory use.
Tom Moreau wrote:[vbcol=seagreen]
>What happens if you set the min server memory and restart SQL Server?
>Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
>Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Window
s
>NT 5.2 (Build 3790: Service Pack 1)
>Tom Moreau wrote:
>[quoted text clipped - 7 lines]
Message posted via http://www.droptable.com|||In SQL 2005, server memory will gradually climb to the max server memory,
whether or not you're using AWE. In SQL 2000, it's supposed to take it in
one chunk, IIRC. I'm thinking that if max = min = whatever you really want,
then you may be forcing it up to that level straight away.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
.
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:6641520a8602d@.uwe...
I am away from the office and will not have access to the server until
tomorrow around 10:00 MST. Even then we will not be able to restart the
service until late tomorrow evening. Do you have a theory about setting "min
server memory"? I believe I recall on the "max server memory" the minimum is
set to 4. Anyway, just trying to follow your thought process on why the "min
server memory" might be inhibiting memory use.
Tom Moreau wrote:[vbcol=seagreen]
>What happens if you set the min server memory and restart SQL Server?
>Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
>Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on
>Windows
>NT 5.2 (Build 3790: Service Pack 1)
>Tom Moreau wrote:
>[quoted text clipped - 7 lines]
Message posted via http://www.droptable.com|||This is the 'expected behavior' of 8.00.2039 and is fixed in 8.00.2040. See
http://support.microsoft.com/defaul...kb;en-us;899761
Linchi
"cbrichards via droptable.com" wrote:
> Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
> Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windo
ws
> NT 5.2 (Build 3790: Service Pack 1)
>
> Tom Moreau wrote:
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200609/1
>
AWE and Target Server Memory
Prior to enabling AWE, we had 8GB RAM but utilizing only 2.7GB.
This is the script we used to enable AWE and set Max Memory, essentially
leaving 2GB for the OS.
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
Just so you are aware, we do have the boot.ini with the PAE and 3GB switches
set.
The question I have, is what I am seeing for Target and Total Server Memory:
Target Server Memory(KB) = 4087767
Total Server Memory(KB) = 4087747
I was expecting to see more Target Server Memory being used (closer to 6GB)
rather than only 4087767KB / 3.898GB.
Please explain.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200609/1Hi,
Do you see the Linch's message ?
This is a SQL Server 2000 Bug after you install SP4, Microsoft recommend
apply following patch:
http://support.microsoft.com/defaul...kb;en-us;899761
Run the following command for see memory status in SQL Server 2000:
DBCC MEMORYSTATUS
For more information see the following KB:
http://support.microsoft.com/?id=271624
Regards,
Rodrigo Fernandes
"cbrichards via droptable.com" wrote:
> Prior to enabling AWE, we had 8GB RAM but utilizing only 2.7GB.
> This is the script we used to enable AWE and set Max Memory, essentially
> leaving 2GB for the OS.
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> sp_configure 'max server memory', 6144
> RECONFIGURE
> GO
> Just so you are aware, we do have the boot.ini with the PAE and 3GB switch
es
> set.
> The question I have, is what I am seeing for Target and Total Server Memor
y:
> Target Server Memory(KB) = 4087767
> Total Server Memory(KB) = 4087747
> I was expecting to see more Target Server Memory being used (closer to 6GB
)
> rather than only 4087767KB / 3.898GB.
> Please explain.
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200609/1
>
This is the script we used to enable AWE and set Max Memory, essentially
leaving 2GB for the OS.
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
Just so you are aware, we do have the boot.ini with the PAE and 3GB switches
set.
The question I have, is what I am seeing for Target and Total Server Memory:
Target Server Memory(KB) = 4087767
Total Server Memory(KB) = 4087747
I was expecting to see more Target Server Memory being used (closer to 6GB)
rather than only 4087767KB / 3.898GB.
Please explain.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200609/1Hi,
Do you see the Linch's message ?
This is a SQL Server 2000 Bug after you install SP4, Microsoft recommend
apply following patch:
http://support.microsoft.com/defaul...kb;en-us;899761
Run the following command for see memory status in SQL Server 2000:
DBCC MEMORYSTATUS
For more information see the following KB:
http://support.microsoft.com/?id=271624
Regards,
Rodrigo Fernandes
"cbrichards via droptable.com" wrote:
> Prior to enabling AWE, we had 8GB RAM but utilizing only 2.7GB.
> This is the script we used to enable AWE and set Max Memory, essentially
> leaving 2GB for the OS.
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> sp_configure 'max server memory', 6144
> RECONFIGURE
> GO
> Just so you are aware, we do have the boot.ini with the PAE and 3GB switch
es
> set.
> The question I have, is what I am seeing for Target and Total Server Memor
y:
> Target Server Memory(KB) = 4087767
> Total Server Memory(KB) = 4087747
> I was expecting to see more Target Server Memory being used (closer to 6GB
)
> rather than only 4087767KB / 3.898GB.
> Please explain.
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200609/1
>
AWE and Target Server Memory
Prior to enabling AWE, we had 8GB RAM but utilizing only 2.7GB.
This is the script we used to enable AWE and set Max Memory, essentially
leaving 2GB for the OS.
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
Just so you are aware, we do have the boot.ini with the PAE and 3GB switches
set.
The question I have, is what I am seeing for Target and Total Server Memory:
Target Server Memory(KB) = 4087767
Total Server Memory(KB) = 4087747
I was expecting to see more Target Server Memory being used (closer to 6GB)
rather than only 4087767KB / 3.898GB.
Please explain.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200609/1
Hi,
Do you see the Linch's message ?
This is a SQL Server 2000 Bug after you install SP4, Microsoft recommend
apply following patch:
http://support.microsoft.com/default...b;en-us;899761
Run the following command for see memory status in SQL Server 2000:
DBCC MEMORYSTATUS
For more information see the following KB:
http://support.microsoft.com/?id=271624
Regards,
Rodrigo Fernandes
"cbrichards via droptable.com" wrote:
> Prior to enabling AWE, we had 8GB RAM but utilizing only 2.7GB.
> This is the script we used to enable AWE and set Max Memory, essentially
> leaving 2GB for the OS.
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> sp_configure 'max server memory', 6144
> RECONFIGURE
> GO
> Just so you are aware, we do have the boot.ini with the PAE and 3GB switches
> set.
> The question I have, is what I am seeing for Target and Total Server Memory:
> Target Server Memory(KB) = 4087767
> Total Server Memory(KB) = 4087747
> I was expecting to see more Target Server Memory being used (closer to 6GB)
> rather than only 4087767KB / 3.898GB.
> Please explain.
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200609/1
>
This is the script we used to enable AWE and set Max Memory, essentially
leaving 2GB for the OS.
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
Just so you are aware, we do have the boot.ini with the PAE and 3GB switches
set.
The question I have, is what I am seeing for Target and Total Server Memory:
Target Server Memory(KB) = 4087767
Total Server Memory(KB) = 4087747
I was expecting to see more Target Server Memory being used (closer to 6GB)
rather than only 4087767KB / 3.898GB.
Please explain.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200609/1
Hi,
Do you see the Linch's message ?
This is a SQL Server 2000 Bug after you install SP4, Microsoft recommend
apply following patch:
http://support.microsoft.com/default...b;en-us;899761
Run the following command for see memory status in SQL Server 2000:
DBCC MEMORYSTATUS
For more information see the following KB:
http://support.microsoft.com/?id=271624
Regards,
Rodrigo Fernandes
"cbrichards via droptable.com" wrote:
> Prior to enabling AWE, we had 8GB RAM but utilizing only 2.7GB.
> This is the script we used to enable AWE and set Max Memory, essentially
> leaving 2GB for the OS.
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> sp_configure 'max server memory', 6144
> RECONFIGURE
> GO
> Just so you are aware, we do have the boot.ini with the PAE and 3GB switches
> set.
> The question I have, is what I am seeing for Target and Total Server Memory:
> Target Server Memory(KB) = 4087767
> Total Server Memory(KB) = 4087747
> I was expecting to see more Target Server Memory being used (closer to 6GB)
> rather than only 4087767KB / 3.898GB.
> Please explain.
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200609/1
>
AWE and Target Server Memory
Prior to enabling AWE, we had 8GB RAM but utilizing only 2.7GB.
This is the script we used to enable AWE and set Max Memory, essentially
leaving 2GB for the OS.
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
Just so you are aware, we do have the boot.ini with the PAE and 3GB switches
set.
The question I have, is what I am seeing for Target and Total Server Memory:
Target Server Memory(KB) = 4087767
Total Server Memory(KB) = 4087747
I was expecting to see more Target Server Memory being used (closer to 6GB)
rather than only 4087767KB / 3.898GB.
Please explain.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200609/1
What version of SQL Server are you using?
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
..
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:663faf808d6ce@.uwe...
Prior to enabling AWE, we had 8GB RAM but utilizing only 2.7GB.
This is the script we used to enable AWE and set Max Memory, essentially
leaving 2GB for the OS.
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
Just so you are aware, we do have the boot.ini with the PAE and 3GB switches
set.
The question I have, is what I am seeing for Target and Total Server Memory:
Target Server Memory(KB) = 4087767
Total Server Memory(KB) = 4087747
I was expecting to see more Target Server Memory being used (closer to 6GB)
rather than only 4087767KB / 3.898GB.
Please explain.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200609/1
|||SQL 2000
Tom Moreau wrote:
>What version of SQL Server are you using?
>Prior to enabling AWE, we had 8GB RAM but utilizing only 2.7GB.
>This is the script we used to enable AWE and set Max Memory, essentially
>leaving 2GB for the OS.
>sp_configure 'show advanced options', 1
>RECONFIGURE
>GO
>sp_configure 'awe enabled', 1
>RECONFIGURE
>GO
>sp_configure 'max server memory', 6144
>RECONFIGURE
>GO
>Just so you are aware, we do have the boot.ini with the PAE and 3GB switches
>set.
>The question I have, is what I am seeing for Target and Total Server Memory:
>Target Server Memory(KB) = 4087767
>Total Server Memory(KB) = 4087747
>I was expecting to see more Target Server Memory being used (closer to 6GB)
>rather than only 4087767KB / 3.898GB.
>Please explain.
Message posted via http://www.droptable.com
|||Which SP level? What's the result of running:
SELECT @.@.VERSION
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
..
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:663fdb867f662@.uwe...
SQL 2000
Tom Moreau wrote:
>What version of SQL Server are you using?
>Prior to enabling AWE, we had 8GB RAM but utilizing only 2.7GB.
>This is the script we used to enable AWE and set Max Memory, essentially
>leaving 2GB for the OS.
>sp_configure 'show advanced options', 1
>RECONFIGURE
>GO
>sp_configure 'awe enabled', 1
>RECONFIGURE
>GO
>sp_configure 'max server memory', 6144
>RECONFIGURE
>GO
>Just so you are aware, we do have the boot.ini with the PAE and 3GB
>switches
>set.
>The question I have, is what I am seeing for Target and Total Server
>Memory:
>Target Server Memory(KB) = 4087767
>Total Server Memory(KB) = 4087747
>I was expecting to see more Target Server Memory being used (closer to 6GB)
>rather than only 4087767KB / 3.898GB.
>Please explain.
Message posted via http://www.droptable.com
|||Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows
NT 5.2 (Build 3790: Service Pack 1)
Tom Moreau wrote:[vbcol=seagreen]
>Which SP level? What's the result of running:
>SELECT @.@.VERSION
>SQL 2000
>Tom Moreau wrote:
>[quoted text clipped - 27 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200609/1
|||What happens if you set the min server memory and restart SQL Server?
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
..
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:664097d00a0ed@.uwe...
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows
NT 5.2 (Build 3790: Service Pack 1)
Tom Moreau wrote:[vbcol=seagreen]
>Which SP level? What's the result of running:
>SELECT @.@.VERSION
>SQL 2000
>Tom Moreau wrote:
>[quoted text clipped - 27 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200609/1
|||I am away from the office and will not have access to the server until
tomorrow around 10:00 MST. Even then we will not be able to restart the
service until late tomorrow evening. Do you have a theory about setting "min
server memory"? I believe I recall on the "max server memory" the minimum is
set to 4. Anyway, just trying to follow your thought process on why the "min
server memory" might be inhibiting memory use.
Tom Moreau wrote:[vbcol=seagreen]
>What happens if you set the min server memory and restart SQL Server?
>Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
>Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows
>NT 5.2 (Build 3790: Service Pack 1)
>Tom Moreau wrote:
>[quoted text clipped - 7 lines]
Message posted via http://www.droptable.com
|||In SQL 2005, server memory will gradually climb to the max server memory,
whether or not you're using AWE. In SQL 2000, it's supposed to take it in
one chunk, IIRC. I'm thinking that if max = min = whatever you really want,
then you may be forcing it up to that level straight away.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
..
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:6641520a8602d@.uwe...
I am away from the office and will not have access to the server until
tomorrow around 10:00 MST. Even then we will not be able to restart the
service until late tomorrow evening. Do you have a theory about setting "min
server memory"? I believe I recall on the "max server memory" the minimum is
set to 4. Anyway, just trying to follow your thought process on why the "min
server memory" might be inhibiting memory use.
Tom Moreau wrote:[vbcol=seagreen]
>What happens if you set the min server memory and restart SQL Server?
>Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
>Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on
>Windows
>NT 5.2 (Build 3790: Service Pack 1)
>Tom Moreau wrote:
>[quoted text clipped - 7 lines]
Message posted via http://www.droptable.com
|||This is the 'expected behavior' of 8.00.2039 and is fixed in 8.00.2040. See
http://support.microsoft.com/default...b;en-us;899761
Linchi
"cbrichards via droptable.com" wrote:
> Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
> Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows
> NT 5.2 (Build 3790: Service Pack 1)
>
> Tom Moreau wrote:
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200609/1
>
This is the script we used to enable AWE and set Max Memory, essentially
leaving 2GB for the OS.
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
Just so you are aware, we do have the boot.ini with the PAE and 3GB switches
set.
The question I have, is what I am seeing for Target and Total Server Memory:
Target Server Memory(KB) = 4087767
Total Server Memory(KB) = 4087747
I was expecting to see more Target Server Memory being used (closer to 6GB)
rather than only 4087767KB / 3.898GB.
Please explain.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200609/1
What version of SQL Server are you using?
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
..
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:663faf808d6ce@.uwe...
Prior to enabling AWE, we had 8GB RAM but utilizing only 2.7GB.
This is the script we used to enable AWE and set Max Memory, essentially
leaving 2GB for the OS.
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
Just so you are aware, we do have the boot.ini with the PAE and 3GB switches
set.
The question I have, is what I am seeing for Target and Total Server Memory:
Target Server Memory(KB) = 4087767
Total Server Memory(KB) = 4087747
I was expecting to see more Target Server Memory being used (closer to 6GB)
rather than only 4087767KB / 3.898GB.
Please explain.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200609/1
|||SQL 2000
Tom Moreau wrote:
>What version of SQL Server are you using?
>Prior to enabling AWE, we had 8GB RAM but utilizing only 2.7GB.
>This is the script we used to enable AWE and set Max Memory, essentially
>leaving 2GB for the OS.
>sp_configure 'show advanced options', 1
>RECONFIGURE
>GO
>sp_configure 'awe enabled', 1
>RECONFIGURE
>GO
>sp_configure 'max server memory', 6144
>RECONFIGURE
>GO
>Just so you are aware, we do have the boot.ini with the PAE and 3GB switches
>set.
>The question I have, is what I am seeing for Target and Total Server Memory:
>Target Server Memory(KB) = 4087767
>Total Server Memory(KB) = 4087747
>I was expecting to see more Target Server Memory being used (closer to 6GB)
>rather than only 4087767KB / 3.898GB.
>Please explain.
Message posted via http://www.droptable.com
|||Which SP level? What's the result of running:
SELECT @.@.VERSION
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
..
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:663fdb867f662@.uwe...
SQL 2000
Tom Moreau wrote:
>What version of SQL Server are you using?
>Prior to enabling AWE, we had 8GB RAM but utilizing only 2.7GB.
>This is the script we used to enable AWE and set Max Memory, essentially
>leaving 2GB for the OS.
>sp_configure 'show advanced options', 1
>RECONFIGURE
>GO
>sp_configure 'awe enabled', 1
>RECONFIGURE
>GO
>sp_configure 'max server memory', 6144
>RECONFIGURE
>GO
>Just so you are aware, we do have the boot.ini with the PAE and 3GB
>switches
>set.
>The question I have, is what I am seeing for Target and Total Server
>Memory:
>Target Server Memory(KB) = 4087767
>Total Server Memory(KB) = 4087747
>I was expecting to see more Target Server Memory being used (closer to 6GB)
>rather than only 4087767KB / 3.898GB.
>Please explain.
Message posted via http://www.droptable.com
|||Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows
NT 5.2 (Build 3790: Service Pack 1)
Tom Moreau wrote:[vbcol=seagreen]
>Which SP level? What's the result of running:
>SELECT @.@.VERSION
>SQL 2000
>Tom Moreau wrote:
>[quoted text clipped - 27 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200609/1
|||What happens if you set the min server memory and restart SQL Server?
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
..
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:664097d00a0ed@.uwe...
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows
NT 5.2 (Build 3790: Service Pack 1)
Tom Moreau wrote:[vbcol=seagreen]
>Which SP level? What's the result of running:
>SELECT @.@.VERSION
>SQL 2000
>Tom Moreau wrote:
>[quoted text clipped - 27 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200609/1
|||I am away from the office and will not have access to the server until
tomorrow around 10:00 MST. Even then we will not be able to restart the
service until late tomorrow evening. Do you have a theory about setting "min
server memory"? I believe I recall on the "max server memory" the minimum is
set to 4. Anyway, just trying to follow your thought process on why the "min
server memory" might be inhibiting memory use.
Tom Moreau wrote:[vbcol=seagreen]
>What happens if you set the min server memory and restart SQL Server?
>Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
>Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows
>NT 5.2 (Build 3790: Service Pack 1)
>Tom Moreau wrote:
>[quoted text clipped - 7 lines]
Message posted via http://www.droptable.com
|||In SQL 2005, server memory will gradually climb to the max server memory,
whether or not you're using AWE. In SQL 2000, it's supposed to take it in
one chunk, IIRC. I'm thinking that if max = min = whatever you really want,
then you may be forcing it up to that level straight away.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
..
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:6641520a8602d@.uwe...
I am away from the office and will not have access to the server until
tomorrow around 10:00 MST. Even then we will not be able to restart the
service until late tomorrow evening. Do you have a theory about setting "min
server memory"? I believe I recall on the "max server memory" the minimum is
set to 4. Anyway, just trying to follow your thought process on why the "min
server memory" might be inhibiting memory use.
Tom Moreau wrote:[vbcol=seagreen]
>What happens if you set the min server memory and restart SQL Server?
>Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
>Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on
>Windows
>NT 5.2 (Build 3790: Service Pack 1)
>Tom Moreau wrote:
>[quoted text clipped - 7 lines]
Message posted via http://www.droptable.com
|||This is the 'expected behavior' of 8.00.2039 and is fixed in 8.00.2040. See
http://support.microsoft.com/default...b;en-us;899761
Linchi
"cbrichards via droptable.com" wrote:
> Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
> Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows
> NT 5.2 (Build 3790: Service Pack 1)
>
> Tom Moreau wrote:
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200609/1
>
Subscribe to:
Posts (Atom)