AWE question (Geoff N. Hiten)

Hello
We have windows 2003 server (8GB) with SQL Server 2004(sp4) +one small
application installed on it.
We also have \3gb parameter in the boot.ini
It is a cluster Active/Passive
What would you recommenf to insttall a hotfix to Passive first and then
Active or it does not matter?
Is it any problems installing a hotfix? What is about lock pages in memory?
And running AWE enabling on Passive first also?
Geoff , how much memory to give to SQL SERVER if small application is using
about 50MB AND SQL SERVER 2.7gb?
Thanks
Alex,
There is no SQL 2004. I am guessing since you mention SP4, that is SQL
2000, since SQL 2005 is only at SP2 for now.
Hotfixes install to all nodes on a cluster for a particular instance. You
need to start the install from the node that is currently hosting the
instance. You must grant lock pages in memory to the SQL service account in
order to get AWE to work. AWE is a setting for the SQL instance, so it will
take effect whichever node hosts that instance.
For an 8GB system, I would start by setting SQL at 6GB and see how free
memory looks. You may be able to inch it up a bit, but it is better to
leave a little extra free memory than to run out. The only down side is
with SQL 2000 you have to stop and restart the service to enact an AWE
memory change.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Alex" <test@.hotmail.com> wrote in message
news:ehk91SwkHHA.4248@.TK2MSFTNGP06.phx.gbl...
> Hello
> We have windows 2003 server (8GB) with SQL Server 2004(sp4) +one small
> application installed on it.
> We also have \3gb parameter in the boot.ini
>
> It is a cluster Active/Passive
> What would you recommenf to insttall a hotfix to Passive first and then
> Active or it does not matter?
> Is it any problems installing a hotfix? What is about lock pages in
> memory?
> And running AWE enabling on Passive first also?
>
> Geoff , how much memory to give to SQL SERVER if small application is
> using about 50MB AND SQL SERVER 2.7gb?
> Thanks
>
>
|||Thank you Geoff N. Hiten
Yes , we are using SQL Server 2000(SP4).
Please take alook at the follwing list and tell me whether it looks good to
you.
a) SQL node1 --(Active) has 8GB
b) SQL node1 --(Passive) has 8GB
1) Install hotfix from(http://support.microsoft.com/kb/899761) on SQL1 node
(Active)
2) Install hotfix from(http://support.microsoft.com/kb/899761) on SQL2 node
(Passive)
3) Grant 'lock pages in memory' on on SQL1 node (Active)
4) Grant 'lock pages in memory' on on SQL1 node (Passive)
5) Enabling AWE on SQL1 node (Active)--set to 6GB
6) Enabling AWE on SQL1 node (Passive)--set to 6GB
Thanks you again
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OZ4pcewkHHA.4904@.TK2MSFTNGP05.phx.gbl...
> Alex,
> There is no SQL 2004. I am guessing since you mention SP4, that is SQL
> 2000, since SQL 2005 is only at SP2 for now.
> Hotfixes install to all nodes on a cluster for a particular instance. You
> need to start the install from the node that is currently hosting the
> instance. You must grant lock pages in memory to the SQL service account
> in order to get AWE to work. AWE is a setting for the SQL instance, so it
> will take effect whichever node hosts that instance.
> For an 8GB system, I would start by setting SQL at 6GB and see how free
> memory looks. You may be able to inch it up a bit, but it is better to
> leave a little extra free memory than to run out. The only down side is
> with SQL 2000 you have to stop and restart the service to enact an AWE
> memory change.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Alex" <test@.hotmail.com> wrote in message
> news:ehk91SwkHHA.4248@.TK2MSFTNGP06.phx.gbl...
>

AWE question (Geoff N. Hiten)

Hello
We have windows 2003 server (8GB) with SQL Server 2004(sp4) +one small
application installed on it.
We also have \3gb parameter in the boot.ini
It is a cluster Active/Passive
What would you recommenf to insttall a hotfix to Passive first and then
Active or it does not matter?
Is it any problems installing a hotfix? What is about lock pages in memory?
And running AWE enabling on Passive first also?
Geoff , how much memory to give to SQL SERVER if small application is using
about 50MB AND SQL SERVER 2.7gb?
ThanksAlex,
There is no SQL 2004. I am guessing since you mention SP4, that is SQL
2000, since SQL 2005 is only at SP2 for now.
Hotfixes install to all nodes on a cluster for a particular instance. You
need to start the install from the node that is currently hosting the
instance. You must grant lock pages in memory to the SQL service account in
order to get AWE to work. AWE is a setting for the SQL instance, so it will
take effect whichever node hosts that instance.
For an 8GB system, I would start by setting SQL at 6GB and see how free
memory looks. You may be able to inch it up a bit, but it is better to
leave a little extra free memory than to run out. The only down side is
with SQL 2000 you have to stop and restart the service to enact an AWE
memory change.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Alex" <test@.hotmail.com> wrote in message
news:ehk91SwkHHA.4248@.TK2MSFTNGP06.phx.gbl...
> Hello
> We have windows 2003 server (8GB) with SQL Server 2004(sp4) +one small
> application installed on it.
> We also have \3gb parameter in the boot.ini
>
> It is a cluster Active/Passive
> What would you recommenf to insttall a hotfix to Passive first and then
> Active or it does not matter?
> Is it any problems installing a hotfix? What is about lock pages in
> memory?
> And running AWE enabling on Passive first also?
>
> Geoff , how much memory to give to SQL SERVER if small application is
> using about 50MB AND SQL SERVER 2.7gb?
> Thanks
>
>|||Thank you Geoff N. Hiten
Yes , we are using SQL Server 2000(SP4).
Please take alook at the follwing list and tell me whether it looks good to
you.
a) SQL node1 --(Active) has 8GB
b) SQL node1 --(Passive) has 8GB
1) Install hotfix from(http://support.microsoft.com/kb/899761) on SQL1 node
(Active)
2) Install hotfix from(http://support.microsoft.com/kb/899761) on SQL2 node
(Passive)
3) Grant 'lock pages in memory' on on SQL1 node (Active)
4) Grant 'lock pages in memory' on on SQL1 node (Passive)
5) Enabling AWE on SQL1 node (Active)--set to 6GB
6) Enabling AWE on SQL1 node (Passive)--set to 6GB
Thanks you again
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OZ4pcewkHHA.4904@.TK2MSFTNGP05.phx.gbl...
> Alex,
> There is no SQL 2004. I am guessing since you mention SP4, that is SQL
> 2000, since SQL 2005 is only at SP2 for now.
> Hotfixes install to all nodes on a cluster for a particular instance. You
> need to start the install from the node that is currently hosting the
> instance. You must grant lock pages in memory to the SQL service account
> in order to get AWE to work. AWE is a setting for the SQL instance, so it
> will take effect whichever node hosts that instance.
> For an 8GB system, I would start by setting SQL at 6GB and see how free
> memory looks. You may be able to inch it up a bit, but it is better to
> leave a little extra free memory than to run out. The only down side is
> with SQL 2000 you have to stop and restart the service to enact an AWE
> memory change.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Alex" <test@.hotmail.com> wrote in message
> news:ehk91SwkHHA.4248@.TK2MSFTNGP06.phx.gbl...
>

AWE Memory

Hello
We have 2 servers in a cluster environment with 12 GB each. We install
SQL server 2000 in them and use the switches /3GB /PAE and use AWE enable
option. We allocated 7GB for SQL along with enough room for the OS and other
apps currently running on that box. My question is, when I check the Task
manager, it only shows that SQL uses 150Kb for memory although you can see
under memory counters that 7.5 is been used. Why can we not see SQL using
more that 150KB? is there anything wrong in our setting? Below are the Store
procedures used to enable AWE and allocate 7GB.
SP_CONFIGURE 'show advanced options', 1
RECONFIGURE
GO
SP_CONFIGURE 'awe enabled', 1
RECONFIGURE
GO
SP_CONFIGURE 'max server memory', 7168
RECONFIGURE
GO
Thanks
Firstly... if you have AWE, you dont need /3GB switch
Now coming to your question: SQL Server when its started it starts
taking memory from 1KB and grows as the resources need more memory...
and once it reaches min server memory, it will never go back to less
than Min Server memory..until you restart the SQL again.
And by configuring 7GB as Max Server memory, you are limiting the SQL
to not consume more than that...
And incase in some scenerio where SQL has any amount of memory and if
OS need some of that.. it will release that memory only if SQL doesnt
need that at that point of time.
So if you see that SQL is using only 150KB, then dont be alarmed.. its
expected behaviour
|||Task manager isn't AWE/PAE aware. Use performance monitor.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Dario" <Dario@.discussions.microsoft.com> wrote in message
news:CF884EB2-F09C-4412-8FC9-547CFC6844CC@.microsoft.com...
> Hello
> We have 2 servers in a cluster environment with 12 GB each. We install
> SQL server 2000 in them and use the switches /3GB /PAE and use AWE enable
> option. We allocated 7GB for SQL along with enough room for the OS and other
> apps currently running on that box. My question is, when I check the Task
> manager, it only shows that SQL uses 150Kb for memory although you can see
> under memory counters that 7.5 is been used. Why can we not see SQL using
> more that 150KB? is there anything wrong in our setting? Below are the Store
> procedures used to enable AWE and allocate 7GB.
> SP_CONFIGURE 'show advanced options', 1
> RECONFIGURE
> GO
> SP_CONFIGURE 'awe enabled', 1
> RECONFIGURE
> GO
> SP_CONFIGURE 'max server memory', 7168
> RECONFIGURE
> GO
> Thanks
>
>

AWE Memory

Hello
We have 2 servers in a cluster environment with 12 GB each. We install
SQL server 2000 in them and use the switches /3GB /PAE and use AWE enable
option. We allocated 7GB for SQL along with enough room for the OS and other
apps currently running on that box. My question is, when I check the Task
manager, it only shows that SQL uses 150Kb for memory although you can see
under memory counters that 7.5 is been used. Why can we not see SQL using
more that 150KB? is there anything wrong in our setting? Below are the Store
procedures used to enable AWE and allocate 7GB.
SP_CONFIGURE 'show advanced options', 1
RECONFIGURE
GO
SP_CONFIGURE 'awe enabled', 1
RECONFIGURE
GO
SP_CONFIGURE 'max server memory', 7168
RECONFIGURE
GO
ThanksFirstly... if you have AWE, you dont need /3GB switch
Now coming to your question: SQL Server when its started it starts
taking memory from 1KB and grows as the resources need more memory...
and once it reaches min server memory, it will never go back to less
than Min Server memory..until you restart the SQL again.
And by configuring 7GB as Max Server memory, you are limiting the SQL
to not consume more than that...
And incase in some scenerio where SQL has any amount of memory and if
OS need some of that.. it will release that memory only if SQL doesnt
need that at that point of time.
So if you see that SQL is using only 150KB, then dont be alarmed.. its
expected behaviour|||Task manager isn't AWE/PAE aware. Use performance monitor.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Dario" <Dario@.discussions.microsoft.com> wrote in message
news:CF884EB2-F09C-4412-8FC9-547CFC6844CC@.microsoft.com...
> Hello
> We have 2 servers in a cluster environment with 12 GB each. We instal
l
> SQL server 2000 in them and use the switches /3GB /PAE and use AWE enable
> option. We allocated 7GB for SQL along with enough room for the OS and oth
er
> apps currently running on that box. My question is, when I check the Task
> manager, it only shows that SQL uses 150Kb for memory although you can see
> under memory counters that 7.5 is been used. Why can we not see SQL using
> more that 150KB? is there anything wrong in our setting? Below are the Sto
re
> procedures used to enable AWE and allocate 7GB.
> SP_CONFIGURE 'show advanced options', 1
> RECONFIGURE
> GO
> SP_CONFIGURE 'awe enabled', 1
> RECONFIGURE
> GO
> SP_CONFIGURE 'max server memory', 7168
> RECONFIGURE
> GO
> Thanks
>
>