Hi
I'm a little confused how best to setup a new 2005 deployment. I'm
moving from a 2000 environment, which used Legato's AAM software to
support failover. The new environment will use MS clustering.
The 2000 setup has multiple instances on each node, and each instance
can run on 3 out of 4 of the 4-node setup. With MS, it looks like each
instance has to have it's own 'virtual server'. So, in this setup,
named instances seem a bit redundant, since you can name the virtual
server. EG Why use Server1\Inst1, Server2\Inst2, when
Server1\<default>, Server2\<default> is just as informative
So, my questions are: 1) is it good practice to use named instances in
a clustered setup;
and 2) what is the rationale behind restricting a virtual server to a
single instance
Thanks.
You only get one default instance per cluster, not per virtual server.
Personally, I only use named instances to avoid name style confusion.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"steve" <stevester@.freeuk.com> wrote in message
news:e4c23b50-bc07-450c-94f7-b71ed051c4bc@.e67g2000hsc.googlegroups.com...
> Hi
> I'm a little confused how best to setup a new 2005 deployment. I'm
> moving from a 2000 environment, which used Legato's AAM software to
> support failover. The new environment will use MS clustering.
> The 2000 setup has multiple instances on each node, and each instance
> can run on 3 out of 4 of the 4-node setup. With MS, it looks like each
> instance has to have it's own 'virtual server'. So, in this setup,
> named instances seem a bit redundant, since you can name the virtual
> server. EG Why use Server1\Inst1, Server2\Inst2, when
> Server1\<default>, Server2\<default> is just as informative
> So, my questions are: 1) is it good practice to use named instances in
> a clustered setup;
> and 2) what is the rationale behind restricting a virtual server to a
> single instance
> Thanks.
|||On 3 Dec, 14:23, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
> You only get one default instance per cluster, not per virtual server.
> Personally, I only use named instances to avoid name style confusion.
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
> "steve" <steves...@.freeuk.com> wrote in message
> news:e4c23b50-bc07-450c-94f7-b71ed051c4bc@.e67g2000hsc.googlegroups.com...
>
>
>
>
> - Show quoted text -
Thanks Geoff. So I can't use deafult instances with each additional
virtual server.
I'm still puzzled why you can only have one instance per virtual
server tho. - seems overly restrictive.
|||It has to do with how SQL organizes binaries for different instances. Or
mor accurately, how multiple instances were handled in SQL 2000.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"steve" <stevester@.freeuk.com> wrote in message
news:1a8e02f1-ca6b-44b3-84ee-b0589802b2c8@.j20g2000hsi.googlegroups.com...
> On 3 Dec, 14:23, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
> Thanks Geoff. So I can't use deafult instances with each additional
> virtual server.
> I'm still puzzled why you can only have one instance per virtual
> server tho. - seems overly restrictive.
|||"steve" <stevester@.freeuk.com> wrote in message
news:e4c23b50-bc07-450c-94f7-b71ed051c4bc@.e67g2000hsc.googlegroups.com...
> The 2000 setup has multiple instances on each node, and each instance
> can run on 3 out of 4 of the 4-node setup. With MS, it looks like each
> instance has to have it's own 'virtual server'. So, in this setup,
> named instances seem a bit redundant, since you can name the virtual
> server. EG Why use Server1\Inst1, Server2\Inst2, when
> Server1\<default>, Server2\<default> is just as informative
Each virtual server must be an instance. You can only have one default
instance per cluster and the rest have to be named instances.
> So, my questions are: 1) is it good practice to use named instances in
> a clustered setup;
You should only used named instances in a cluster. There are some known
issues around patching that can cause problems, for example, if you service
pack a named instance before the default.
> and 2) what is the rationale behind restricting a virtual server to a
> single instance
Each instance requires its own resources, thus, each requires its own
virtual server.
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp
The next ClusterHelp classes are:
Dec 10 - 13 in Denver
Jan 18 - 31 in Denver
|||Thanks for your answers - very helpful.
Steve
Showing posts with label w2k3. Show all posts
Showing posts with label w2k3. Show all posts
Friday, February 24, 2012
Thursday, February 16, 2012
Clustered W2K3 Server Memory
Hi,
We have a W2K3 cluster with 3.6Gb memory on each of the 2 servers running
SQL2000 SP3A. We have the /PAE switch on in the boot.ini files on both
nodes. Is SQL2000 able to use more than 2Gb of memory, with this setting, or
do we need the /3GB switch as well with maybe a /USERRVA setting?
Thanks
Chris Wood
Alberta Department of Energy
CANADA
/PAE will only be useful if you have over 4Gb Memory . . unfortunately this
switch is redundant is this situation given your memory configuration.
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:ez6Nyiq8EHA.2060@.TK2MSFTNGP10.phx.gbl...
> Hi,
> We have a W2K3 cluster with 3.6Gb memory on each of the 2 servers running
> SQL2000 SP3A. We have the /PAE switch on in the boot.ini files on both
> nodes. Is SQL2000 able to use more than 2Gb of memory, with this setting,
or
> do we need the /3GB switch as well with maybe a /USERRVA setting?
> Thanks
> Chris Wood
> Alberta Department of Energy
> CANADA
>
|||Yes the /3GB would be required if you wanted to use more than 2GB for SQL
Server. The /PAE is not used until you have > 4GB.
Andrew J. Kelly SQL MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:ez6Nyiq8EHA.2060@.TK2MSFTNGP10.phx.gbl...
> Hi,
> We have a W2K3 cluster with 3.6Gb memory on each of the 2 servers running
> SQL2000 SP3A. We have the /PAE switch on in the boot.ini files on both
> nodes. Is SQL2000 able to use more than 2Gb of memory, with this setting,
> or
> do we need the /3GB switch as well with maybe a /USERRVA setting?
> Thanks
> Chris Wood
> Alberta Department of Energy
> CANADA
>
|||Andrew,
Just want to make sure of this as some of our Windows people think that W2K3
is different than W2K for using /3Gb switch.
I have reviewed a number of KB article and it is as clear as mud but I
believe that the /3Gb switch works the same way as in W2K and we would need
it in Boot.Ini for SQL to use more than 2Gb.
Thanks
Chris
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:ufFb8es8EHA.1392@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> Yes the /3GB would be required if you wanted to use more than 2GB for SQL
> Server. The /PAE is not used until you have > 4GB.
> --
> Andrew J. Kelly SQL MVP
>
> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
> news:ez6Nyiq8EHA.2060@.TK2MSFTNGP10.phx.gbl...
running[vbcol=seagreen]
setting,
>
|||I am actually having a brain fart<g> at the moment as I can't recall what I
want to answer you properly. There is something about Win2K3 that it does
automatically but I think it is the setting of the /PAE switch and not /3GB.
I believe the /3GB is still required to be set manually.
Andrew J. Kelly SQL MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:uF$n$w08EHA.3700@.tk2msftngp13.phx.gbl...
> Andrew,
> Just want to make sure of this as some of our Windows people think that
> W2K3
> is different than W2K for using /3Gb switch.
> I have reviewed a number of KB article and it is as clear as mud but I
> believe that the /3Gb switch works the same way as in W2K and we would
> need
> it in Boot.Ini for SQL to use more than 2Gb.
> Thanks
> Chris
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:ufFb8es8EHA.1392@.tk2msftngp13.phx.gbl...
> running
> setting,
>
|||Andrew,
If you can remember that would be great. I still have to convince one
analyst that we need the /3Gb switch and not the /PAE switch set.
Thanks
Chris
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eAxdW618EHA.1400@.TK2MSFTNGP11.phx.gbl...
> I am actually having a brain fart<g> at the moment as I can't recall what
I
> want to answer you properly. There is something about Win2K3 that it does
> automatically but I think it is the setting of the /PAE switch and not
/3GB.[vbcol=seagreen]
> I believe the /3GB is still required to be set manually.
> --
> Andrew J. Kelly SQL MVP
>
> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
> news:uF$n$w08EHA.3700@.tk2msftngp13.phx.gbl...
SQL[vbcol=seagreen]
both
>
|||Well if they try it without the /3GB and it doesn't give you more than 2GB
it obviously wont work<g>. I will see if I can dig that up.
Andrew J. Kelly SQL MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:%23P58gmA9EHA.3236@.TK2MSFTNGP15.phx.gbl...
> Andrew,
> If you can remember that would be great. I still have to convince one
> analyst that we need the /3Gb switch and not the /PAE switch set.
> Thanks
> Chris
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:eAxdW618EHA.1400@.TK2MSFTNGP11.phx.gbl...
> I
> /3GB.
> SQL
> both
>
|||Andrew,
I may have found the answer in KB 838765. It mentions under point 6 of
Workaround
Note On a computer that is running Windows Server 2003 the PAE specification
is automatically turned on if the computer is configured to use hot-add
memory devices.
Not sure how I can see if the option is set.
Chris
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:unegDGB9EHA.3416@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Well if they try it without the /3GB and it doesn't give you more than 2GB
> it obviously wont work<g>. I will see if I can dig that up.
>
> --
> Andrew J. Kelly SQL MVP
>
> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
> news:%23P58gmA9EHA.3236@.TK2MSFTNGP15.phx.gbl...
what[vbcol=seagreen]
that[vbcol=seagreen]
I[vbcol=seagreen]
would[vbcol=seagreen]
for
>
|||I was pretty sure this was the case although I don't recall ever seeing the
condition of Hot Add memory devices. In either case I think it is worth
placing the /PAE in the boot.ini so there is no mistaking. If it happens to
be there already so be it but at least someone went through the exercise to
ensure it was set. I am almost 100% sure the /3GB is a manual option.
Andrew J. Kelly SQL MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:eF3yxxN9EHA.2180@.TK2MSFTNGP12.phx.gbl...
> Andrew,
> I may have found the answer in KB 838765. It mentions under point 6 of
> Workaround
> Note On a computer that is running Windows Server 2003 the PAE
> specification
> is automatically turned on if the computer is configured to use hot-add
> memory devices.
> Not sure how I can see if the option is set.
> Chris
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:unegDGB9EHA.3416@.TK2MSFTNGP09.phx.gbl...
> what
> that
> I
> would
> for
>
|||This is a good one!
Here are two registry keys that you can use to assist you:
HKLM\SYSTEM\CurrentControlSet\Control\SystemStartO ptions, will tell you
which BOOT.INI configuration was choosen as the current startup.
HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory
Management\PhysicalAddressExtensions, will tell you whether or not the PAE
has been enabled for the current startup.
Now, as to your question regarding SQL Server configuration and Win2K3, /3GB
is still required, but there is a new option, /USERVA that will allow you
more granularity of control, BETWEEN 2GB and 3GB, but it REQUIRES the /3GB
to also be present.
/PAE will only assist you with memory above 4GB. All it does is tell the
kernel to use a 36-bit address space, which would give you the ability to
address UP TO 64GB, instead of the default 32-bit address space, which will
allow you to address up to 4GB. Clearly, a 32-bit address is just a subset
of a 36-bit; so, using a 36-bit address space make no sense unless you
actually use the 33rd bit or higher.
If you are using SQL Server Standard Edition, SS will never create a Buffer
Pool larger than 2 GB, period. However, as I have had this conversation
with those here before, SS also uses another memory segment know as MEM TO
LEAVE, which is everything above the 2 GB limit but less than the USER MODE
address space, minus 512MB x Worker Threads, minus -g startup parameter. UM
will be up to 2GB if you have not enabled the /3GB startup option.
So, for SS SE, with the /3GB option enabled and no use of /USERVA, there
will be a 3GB VIRTUAL UM address space. SS SE will create a Buffer Pool of
2GB, maximum, but MEM TO LEAVE will be around 1GB - 384MB. If you have
sufficient physical ram, then most of this will be real memory, but there
will always be some swap space usage.
Now, for Enterprise Edition. What is different here is the ability to use
the AWE features, but also, the real Buffer Pool can also be extended to the
full UM address space. So, with between 2GB and 4GB of physical memory, you
have two options. You can leave AWE disabled, but extend the real Buffer
Pool up to 3GB, or, you can enable AWE, use up to 3GB for the real Buffer
Pool, minus MEM TO LEAVE, and then use the remainder, up to 1GB, of AWE
address space.
With more than 4GB, then you MUST use PAE, whether or not Win2K3 enables
this for you or not, use the registry settings to determine if it was
detected, but AWE will require PAE to make use of any address space above
4GB. In fact, the OS and SS will not even recognize memory greater than 4GB
even exists without PAE enabled.
Hope this helps.
Sincerely,
Anthony Thomas
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:Oh%23rZCP9EHA.3236@.TK2MSFTNGP15.phx.gbl...
I was pretty sure this was the case although I don't recall ever seeing the
condition of Hot Add memory devices. In either case I think it is worth
placing the /PAE in the boot.ini so there is no mistaking. If it happens to
be there already so be it but at least someone went through the exercise to
ensure it was set. I am almost 100% sure the /3GB is a manual option.
Andrew J. Kelly SQL MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:eF3yxxN9EHA.2180@.TK2MSFTNGP12.phx.gbl...
> Andrew,
> I may have found the answer in KB 838765. It mentions under point 6 of
> Workaround
> Note On a computer that is running Windows Server 2003 the PAE
> specification
> is automatically turned on if the computer is configured to use hot-add
> memory devices.
> Not sure how I can see if the option is set.
> Chris
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:unegDGB9EHA.3416@.TK2MSFTNGP09.phx.gbl...
> what
> that
> I
> would
> for
>
We have a W2K3 cluster with 3.6Gb memory on each of the 2 servers running
SQL2000 SP3A. We have the /PAE switch on in the boot.ini files on both
nodes. Is SQL2000 able to use more than 2Gb of memory, with this setting, or
do we need the /3GB switch as well with maybe a /USERRVA setting?
Thanks
Chris Wood
Alberta Department of Energy
CANADA
/PAE will only be useful if you have over 4Gb Memory . . unfortunately this
switch is redundant is this situation given your memory configuration.
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:ez6Nyiq8EHA.2060@.TK2MSFTNGP10.phx.gbl...
> Hi,
> We have a W2K3 cluster with 3.6Gb memory on each of the 2 servers running
> SQL2000 SP3A. We have the /PAE switch on in the boot.ini files on both
> nodes. Is SQL2000 able to use more than 2Gb of memory, with this setting,
or
> do we need the /3GB switch as well with maybe a /USERRVA setting?
> Thanks
> Chris Wood
> Alberta Department of Energy
> CANADA
>
|||Yes the /3GB would be required if you wanted to use more than 2GB for SQL
Server. The /PAE is not used until you have > 4GB.
Andrew J. Kelly SQL MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:ez6Nyiq8EHA.2060@.TK2MSFTNGP10.phx.gbl...
> Hi,
> We have a W2K3 cluster with 3.6Gb memory on each of the 2 servers running
> SQL2000 SP3A. We have the /PAE switch on in the boot.ini files on both
> nodes. Is SQL2000 able to use more than 2Gb of memory, with this setting,
> or
> do we need the /3GB switch as well with maybe a /USERRVA setting?
> Thanks
> Chris Wood
> Alberta Department of Energy
> CANADA
>
|||Andrew,
Just want to make sure of this as some of our Windows people think that W2K3
is different than W2K for using /3Gb switch.
I have reviewed a number of KB article and it is as clear as mud but I
believe that the /3Gb switch works the same way as in W2K and we would need
it in Boot.Ini for SQL to use more than 2Gb.
Thanks
Chris
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:ufFb8es8EHA.1392@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> Yes the /3GB would be required if you wanted to use more than 2GB for SQL
> Server. The /PAE is not used until you have > 4GB.
> --
> Andrew J. Kelly SQL MVP
>
> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
> news:ez6Nyiq8EHA.2060@.TK2MSFTNGP10.phx.gbl...
running[vbcol=seagreen]
setting,
>
|||I am actually having a brain fart<g> at the moment as I can't recall what I
want to answer you properly. There is something about Win2K3 that it does
automatically but I think it is the setting of the /PAE switch and not /3GB.
I believe the /3GB is still required to be set manually.
Andrew J. Kelly SQL MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:uF$n$w08EHA.3700@.tk2msftngp13.phx.gbl...
> Andrew,
> Just want to make sure of this as some of our Windows people think that
> W2K3
> is different than W2K for using /3Gb switch.
> I have reviewed a number of KB article and it is as clear as mud but I
> believe that the /3Gb switch works the same way as in W2K and we would
> need
> it in Boot.Ini for SQL to use more than 2Gb.
> Thanks
> Chris
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:ufFb8es8EHA.1392@.tk2msftngp13.phx.gbl...
> running
> setting,
>
|||Andrew,
If you can remember that would be great. I still have to convince one
analyst that we need the /3Gb switch and not the /PAE switch set.
Thanks
Chris
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eAxdW618EHA.1400@.TK2MSFTNGP11.phx.gbl...
> I am actually having a brain fart<g> at the moment as I can't recall what
I
> want to answer you properly. There is something about Win2K3 that it does
> automatically but I think it is the setting of the /PAE switch and not
/3GB.[vbcol=seagreen]
> I believe the /3GB is still required to be set manually.
> --
> Andrew J. Kelly SQL MVP
>
> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
> news:uF$n$w08EHA.3700@.tk2msftngp13.phx.gbl...
SQL[vbcol=seagreen]
both
>
|||Well if they try it without the /3GB and it doesn't give you more than 2GB
it obviously wont work<g>. I will see if I can dig that up.
Andrew J. Kelly SQL MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:%23P58gmA9EHA.3236@.TK2MSFTNGP15.phx.gbl...
> Andrew,
> If you can remember that would be great. I still have to convince one
> analyst that we need the /3Gb switch and not the /PAE switch set.
> Thanks
> Chris
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:eAxdW618EHA.1400@.TK2MSFTNGP11.phx.gbl...
> I
> /3GB.
> SQL
> both
>
|||Andrew,
I may have found the answer in KB 838765. It mentions under point 6 of
Workaround
Note On a computer that is running Windows Server 2003 the PAE specification
is automatically turned on if the computer is configured to use hot-add
memory devices.
Not sure how I can see if the option is set.
Chris
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:unegDGB9EHA.3416@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Well if they try it without the /3GB and it doesn't give you more than 2GB
> it obviously wont work<g>. I will see if I can dig that up.
>
> --
> Andrew J. Kelly SQL MVP
>
> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
> news:%23P58gmA9EHA.3236@.TK2MSFTNGP15.phx.gbl...
what[vbcol=seagreen]
that[vbcol=seagreen]
I[vbcol=seagreen]
would[vbcol=seagreen]
for
>
|||I was pretty sure this was the case although I don't recall ever seeing the
condition of Hot Add memory devices. In either case I think it is worth
placing the /PAE in the boot.ini so there is no mistaking. If it happens to
be there already so be it but at least someone went through the exercise to
ensure it was set. I am almost 100% sure the /3GB is a manual option.
Andrew J. Kelly SQL MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:eF3yxxN9EHA.2180@.TK2MSFTNGP12.phx.gbl...
> Andrew,
> I may have found the answer in KB 838765. It mentions under point 6 of
> Workaround
> Note On a computer that is running Windows Server 2003 the PAE
> specification
> is automatically turned on if the computer is configured to use hot-add
> memory devices.
> Not sure how I can see if the option is set.
> Chris
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:unegDGB9EHA.3416@.TK2MSFTNGP09.phx.gbl...
> what
> that
> I
> would
> for
>
|||This is a good one!
Here are two registry keys that you can use to assist you:
HKLM\SYSTEM\CurrentControlSet\Control\SystemStartO ptions, will tell you
which BOOT.INI configuration was choosen as the current startup.
HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory
Management\PhysicalAddressExtensions, will tell you whether or not the PAE
has been enabled for the current startup.
Now, as to your question regarding SQL Server configuration and Win2K3, /3GB
is still required, but there is a new option, /USERVA that will allow you
more granularity of control, BETWEEN 2GB and 3GB, but it REQUIRES the /3GB
to also be present.
/PAE will only assist you with memory above 4GB. All it does is tell the
kernel to use a 36-bit address space, which would give you the ability to
address UP TO 64GB, instead of the default 32-bit address space, which will
allow you to address up to 4GB. Clearly, a 32-bit address is just a subset
of a 36-bit; so, using a 36-bit address space make no sense unless you
actually use the 33rd bit or higher.
If you are using SQL Server Standard Edition, SS will never create a Buffer
Pool larger than 2 GB, period. However, as I have had this conversation
with those here before, SS also uses another memory segment know as MEM TO
LEAVE, which is everything above the 2 GB limit but less than the USER MODE
address space, minus 512MB x Worker Threads, minus -g startup parameter. UM
will be up to 2GB if you have not enabled the /3GB startup option.
So, for SS SE, with the /3GB option enabled and no use of /USERVA, there
will be a 3GB VIRTUAL UM address space. SS SE will create a Buffer Pool of
2GB, maximum, but MEM TO LEAVE will be around 1GB - 384MB. If you have
sufficient physical ram, then most of this will be real memory, but there
will always be some swap space usage.
Now, for Enterprise Edition. What is different here is the ability to use
the AWE features, but also, the real Buffer Pool can also be extended to the
full UM address space. So, with between 2GB and 4GB of physical memory, you
have two options. You can leave AWE disabled, but extend the real Buffer
Pool up to 3GB, or, you can enable AWE, use up to 3GB for the real Buffer
Pool, minus MEM TO LEAVE, and then use the remainder, up to 1GB, of AWE
address space.
With more than 4GB, then you MUST use PAE, whether or not Win2K3 enables
this for you or not, use the registry settings to determine if it was
detected, but AWE will require PAE to make use of any address space above
4GB. In fact, the OS and SS will not even recognize memory greater than 4GB
even exists without PAE enabled.
Hope this helps.
Sincerely,
Anthony Thomas
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:Oh%23rZCP9EHA.3236@.TK2MSFTNGP15.phx.gbl...
I was pretty sure this was the case although I don't recall ever seeing the
condition of Hot Add memory devices. In either case I think it is worth
placing the /PAE in the boot.ini so there is no mistaking. If it happens to
be there already so be it but at least someone went through the exercise to
ensure it was set. I am almost 100% sure the /3GB is a manual option.
Andrew J. Kelly SQL MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:eF3yxxN9EHA.2180@.TK2MSFTNGP12.phx.gbl...
> Andrew,
> I may have found the answer in KB 838765. It mentions under point 6 of
> Workaround
> Note On a computer that is running Windows Server 2003 the PAE
> specification
> is automatically turned on if the computer is configured to use hot-add
> memory devices.
> Not sure how I can see if the option is set.
> Chris
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:unegDGB9EHA.3416@.TK2MSFTNGP09.phx.gbl...
> what
> that
> I
> would
> for
>
Clustered W2K3 Server Memory
Hi,
We have a W2K3 cluster with 3.6Gb memory on each of the 2 servers running
SQL2000 SP3A. We have the /PAE switch on in the boot.ini files on both
nodes. Is SQL2000 able to use more than 2Gb of memory, with this setting, or
do we need the /3GB switch as well with maybe a /USERRVA setting?
Thanks
Chris Wood
Alberta Department of Energy
CANADA/PAE will only be useful if you have over 4Gb Memory . . unfortunately this
switch is redundant is this situation given your memory configuration.
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:ez6Nyiq8EHA.2060@.TK2MSFTNGP10.phx.gbl...
> Hi,
> We have a W2K3 cluster with 3.6Gb memory on each of the 2 servers running
> SQL2000 SP3A. We have the /PAE switch on in the boot.ini files on both
> nodes. Is SQL2000 able to use more than 2Gb of memory, with this setting,
or
> do we need the /3GB switch as well with maybe a /USERRVA setting?
> Thanks
> Chris Wood
> Alberta Department of Energy
> CANADA
>|||Yes the /3GB would be required if you wanted to use more than 2GB for SQL
Server. The /PAE is not used until you have > 4GB.
Andrew J. Kelly SQL MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:ez6Nyiq8EHA.2060@.TK2MSFTNGP10.phx.gbl...
> Hi,
> We have a W2K3 cluster with 3.6Gb memory on each of the 2 servers running
> SQL2000 SP3A. We have the /PAE switch on in the boot.ini files on both
> nodes. Is SQL2000 able to use more than 2Gb of memory, with this setting,
> or
> do we need the /3GB switch as well with maybe a /USERRVA setting?
> Thanks
> Chris Wood
> Alberta Department of Energy
> CANADA
>|||Andrew,
Just want to make sure of this as some of our Windows people think that W2K3
is different than W2K for using /3Gb switch.
I have reviewed a number of KB article and it is as clear as mud but I
believe that the /3Gb switch works the same way as in W2K and we would need
it in Boot.Ini for SQL to use more than 2Gb.
Thanks
Chris
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:ufFb8es8EHA.1392@.tk2msftngp13.phx.gbl...
> Yes the /3GB would be required if you wanted to use more than 2GB for SQL
> Server. The /PAE is not used until you have > 4GB.
> --
> Andrew J. Kelly SQL MVP
>
> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
> news:ez6Nyiq8EHA.2060@.TK2MSFTNGP10.phx.gbl...
running[vbcol=seagreen]
setting,[vbcol=seagreen]
>|||I am actually having a brain fart<g> at the moment as I can't recall what I
want to answer you properly. There is something about Win2K3 that it does
automatically but I think it is the setting of the /PAE switch and not /3GB.
I believe the /3GB is still required to be set manually.
Andrew J. Kelly SQL MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:uF$n$w08EHA.3700@.tk2msftngp13.phx.gbl...
> Andrew,
> Just want to make sure of this as some of our Windows people think that
> W2K3
> is different than W2K for using /3Gb switch.
> I have reviewed a number of KB article and it is as clear as mud but I
> believe that the /3Gb switch works the same way as in W2K and we would
> need
> it in Boot.Ini for SQL to use more than 2Gb.
> Thanks
> Chris
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:ufFb8es8EHA.1392@.tk2msftngp13.phx.gbl...
> running
> setting,
>|||Andrew,
If you can remember that would be great. I still have to convince one
analyst that we need the /3Gb switch and not the /PAE switch set.
Thanks
Chris
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eAxdW618EHA.1400@.TK2MSFTNGP11.phx.gbl...
> I am actually having a brain fart<g> at the moment as I can't recall what
I
> want to answer you properly. There is something about Win2K3 that it does
> automatically but I think it is the setting of the /PAE switch and not
/3GB.
> I believe the /3GB is still required to be set manually.
> --
> Andrew J. Kelly SQL MVP
>
> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
> news:uF$n$w08EHA.3700@.tk2msftngp13.phx.gbl...
SQL[vbcol=seagreen]
both[vbcol=seagreen]
>|||Well if they try it without the /3GB and it doesn't give you more than 2GB
it obviously wont work<g>. I will see if I can dig that up.
Andrew J. Kelly SQL MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:%23P58gmA9EHA.3236@.TK2MSFTNGP15.phx.gbl...
> Andrew,
> If you can remember that would be great. I still have to convince one
> analyst that we need the /3Gb switch and not the /PAE switch set.
> Thanks
> Chris
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:eAxdW618EHA.1400@.TK2MSFTNGP11.phx.gbl...
> I
> /3GB.
> SQL
> both
>|||Andrew,
I may have found the answer in KB 838765. It mentions under point 6 of
Workaround
Note On a computer that is running Windows Server 2003 the PAE specification
is automatically turned on if the computer is configured to use hot-add
memory devices.
Not sure how I can see if the option is set.
Chris
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:unegDGB9EHA.3416@.TK2MSFTNGP09.phx.gbl...
> Well if they try it without the /3GB and it doesn't give you more than 2GB
> it obviously wont work<g>. I will see if I can dig that up.
>
> --
> Andrew J. Kelly SQL MVP
>
> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
> news:%23P58gmA9EHA.3236@.TK2MSFTNGP15.phx.gbl...
what[vbcol=seagreen]
that[vbcol=seagreen]
I[vbcol=seagreen]
would[vbcol=seagreen]
for[vbcol=seagreen]
>|||I was pretty sure this was the case although I don't recall ever seeing the
condition of Hot Add memory devices. In either case I think it is worth
placing the /PAE in the boot.ini so there is no mistaking. If it happens to
be there already so be it but at least someone went through the exercise to
ensure it was set. I am almost 100% sure the /3GB is a manual option.
Andrew J. Kelly SQL MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:eF3yxxN9EHA.2180@.TK2MSFTNGP12.phx.gbl...
> Andrew,
> I may have found the answer in KB 838765. It mentions under point 6 of
> Workaround
> Note On a computer that is running Windows Server 2003 the PAE
> specification
> is automatically turned on if the computer is configured to use hot-add
> memory devices.
> Not sure how I can see if the option is set.
> Chris
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:unegDGB9EHA.3416@.TK2MSFTNGP09.phx.gbl...
> what
> that
> I
> would
> for
>|||This is a good one!
Here are two registry keys that you can use to assist you:
HKLM\SYSTEM\CurrentControlSet\Control\Sy
stemStartOptions, will tell you
which BOOT.INI configuration was choosen as the current startup.
HKLM\SYSTEM\CurrentControlSet\Control\Se
ssion Manager\Memory
Management\PhysicalAddressExtensions, will tell you whether or not the PAE
has been enabled for the current startup.
Now, as to your question regarding SQL Server configuration and Win2K3, /3GB
is still required, but there is a new option, /USERVA that will allow you
more granularity of control, BETWEEN 2GB and 3GB, but it REQUIRES the /3GB
to also be present.
/PAE will only assist you with memory above 4GB. All it does is tell the
kernel to use a 36-bit address space, which would give you the ability to
address UP TO 64GB, instead of the default 32-bit address space, which will
allow you to address up to 4GB. Clearly, a 32-bit address is just a subset
of a 36-bit; so, using a 36-bit address space make no sense unless you
actually use the 33rd bit or higher.
If you are using SQL Server Standard Edition, SS will never create a Buffer
Pool larger than 2 GB, period. However, as I have had this conversation
with those here before, SS also uses another memory segment know as MEM TO
LEAVE, which is everything above the 2 GB limit but less than the USER MODE
address space, minus 512MB x Worker Threads, minus -g startup parameter. UM
will be up to 2GB if you have not enabled the /3GB startup option.
So, for SS SE, with the /3GB option enabled and no use of /USERVA, there
will be a 3GB VIRTUAL UM address space. SS SE will create a Buffer Pool of
2GB, maximum, but MEM TO LEAVE will be around 1GB - 384MB. If you have
sufficient physical ram, then most of this will be real memory, but there
will always be some swap space usage.
Now, for Enterprise Edition. What is different here is the ability to use
the AWE features, but also, the real Buffer Pool can also be extended to the
full UM address space. So, with between 2GB and 4GB of physical memory, you
have two options. You can leave AWE disabled, but extend the real Buffer
Pool up to 3GB, or, you can enable AWE, use up to 3GB for the real Buffer
Pool, minus MEM TO LEAVE, and then use the remainder, up to 1GB, of AWE
address space.
With more than 4GB, then you MUST use PAE, whether or not Win2K3 enables
this for you or not, use the registry settings to determine if it was
detected, but AWE will require PAE to make use of any address space above
4GB. In fact, the OS and SS will not even recognize memory greater than 4GB
even exists without PAE enabled.
Hope this helps.
Sincerely,
Anthony Thomas
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:Oh%23rZCP9EHA.3236@.TK2MSFTNGP15.phx.gbl...
I was pretty sure this was the case although I don't recall ever seeing the
condition of Hot Add memory devices. In either case I think it is worth
placing the /PAE in the boot.ini so there is no mistaking. If it happens to
be there already so be it but at least someone went through the exercise to
ensure it was set. I am almost 100% sure the /3GB is a manual option.
Andrew J. Kelly SQL MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:eF3yxxN9EHA.2180@.TK2MSFTNGP12.phx.gbl...
> Andrew,
> I may have found the answer in KB 838765. It mentions under point 6 of
> Workaround
> Note On a computer that is running Windows Server 2003 the PAE
> specification
> is automatically turned on if the computer is configured to use hot-add
> memory devices.
> Not sure how I can see if the option is set.
> Chris
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:unegDGB9EHA.3416@.TK2MSFTNGP09.phx.gbl...
> what
> that
> I
> would
> for
>
We have a W2K3 cluster with 3.6Gb memory on each of the 2 servers running
SQL2000 SP3A. We have the /PAE switch on in the boot.ini files on both
nodes. Is SQL2000 able to use more than 2Gb of memory, with this setting, or
do we need the /3GB switch as well with maybe a /USERRVA setting?
Thanks
Chris Wood
Alberta Department of Energy
CANADA/PAE will only be useful if you have over 4Gb Memory . . unfortunately this
switch is redundant is this situation given your memory configuration.
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:ez6Nyiq8EHA.2060@.TK2MSFTNGP10.phx.gbl...
> Hi,
> We have a W2K3 cluster with 3.6Gb memory on each of the 2 servers running
> SQL2000 SP3A. We have the /PAE switch on in the boot.ini files on both
> nodes. Is SQL2000 able to use more than 2Gb of memory, with this setting,
or
> do we need the /3GB switch as well with maybe a /USERRVA setting?
> Thanks
> Chris Wood
> Alberta Department of Energy
> CANADA
>|||Yes the /3GB would be required if you wanted to use more than 2GB for SQL
Server. The /PAE is not used until you have > 4GB.
Andrew J. Kelly SQL MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:ez6Nyiq8EHA.2060@.TK2MSFTNGP10.phx.gbl...
> Hi,
> We have a W2K3 cluster with 3.6Gb memory on each of the 2 servers running
> SQL2000 SP3A. We have the /PAE switch on in the boot.ini files on both
> nodes. Is SQL2000 able to use more than 2Gb of memory, with this setting,
> or
> do we need the /3GB switch as well with maybe a /USERRVA setting?
> Thanks
> Chris Wood
> Alberta Department of Energy
> CANADA
>|||Andrew,
Just want to make sure of this as some of our Windows people think that W2K3
is different than W2K for using /3Gb switch.
I have reviewed a number of KB article and it is as clear as mud but I
believe that the /3Gb switch works the same way as in W2K and we would need
it in Boot.Ini for SQL to use more than 2Gb.
Thanks
Chris
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:ufFb8es8EHA.1392@.tk2msftngp13.phx.gbl...
> Yes the /3GB would be required if you wanted to use more than 2GB for SQL
> Server. The /PAE is not used until you have > 4GB.
> --
> Andrew J. Kelly SQL MVP
>
> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
> news:ez6Nyiq8EHA.2060@.TK2MSFTNGP10.phx.gbl...
running[vbcol=seagreen]
setting,[vbcol=seagreen]
>|||I am actually having a brain fart<g> at the moment as I can't recall what I
want to answer you properly. There is something about Win2K3 that it does
automatically but I think it is the setting of the /PAE switch and not /3GB.
I believe the /3GB is still required to be set manually.
Andrew J. Kelly SQL MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:uF$n$w08EHA.3700@.tk2msftngp13.phx.gbl...
> Andrew,
> Just want to make sure of this as some of our Windows people think that
> W2K3
> is different than W2K for using /3Gb switch.
> I have reviewed a number of KB article and it is as clear as mud but I
> believe that the /3Gb switch works the same way as in W2K and we would
> need
> it in Boot.Ini for SQL to use more than 2Gb.
> Thanks
> Chris
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:ufFb8es8EHA.1392@.tk2msftngp13.phx.gbl...
> running
> setting,
>|||Andrew,
If you can remember that would be great. I still have to convince one
analyst that we need the /3Gb switch and not the /PAE switch set.
Thanks
Chris
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eAxdW618EHA.1400@.TK2MSFTNGP11.phx.gbl...
> I am actually having a brain fart<g> at the moment as I can't recall what
I
> want to answer you properly. There is something about Win2K3 that it does
> automatically but I think it is the setting of the /PAE switch and not
/3GB.
> I believe the /3GB is still required to be set manually.
> --
> Andrew J. Kelly SQL MVP
>
> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
> news:uF$n$w08EHA.3700@.tk2msftngp13.phx.gbl...
SQL[vbcol=seagreen]
both[vbcol=seagreen]
>|||Well if they try it without the /3GB and it doesn't give you more than 2GB
it obviously wont work<g>. I will see if I can dig that up.
Andrew J. Kelly SQL MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:%23P58gmA9EHA.3236@.TK2MSFTNGP15.phx.gbl...
> Andrew,
> If you can remember that would be great. I still have to convince one
> analyst that we need the /3Gb switch and not the /PAE switch set.
> Thanks
> Chris
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:eAxdW618EHA.1400@.TK2MSFTNGP11.phx.gbl...
> I
> /3GB.
> SQL
> both
>|||Andrew,
I may have found the answer in KB 838765. It mentions under point 6 of
Workaround
Note On a computer that is running Windows Server 2003 the PAE specification
is automatically turned on if the computer is configured to use hot-add
memory devices.
Not sure how I can see if the option is set.
Chris
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:unegDGB9EHA.3416@.TK2MSFTNGP09.phx.gbl...
> Well if they try it without the /3GB and it doesn't give you more than 2GB
> it obviously wont work<g>. I will see if I can dig that up.
>
> --
> Andrew J. Kelly SQL MVP
>
> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
> news:%23P58gmA9EHA.3236@.TK2MSFTNGP15.phx.gbl...
what[vbcol=seagreen]
that[vbcol=seagreen]
I[vbcol=seagreen]
would[vbcol=seagreen]
for[vbcol=seagreen]
>|||I was pretty sure this was the case although I don't recall ever seeing the
condition of Hot Add memory devices. In either case I think it is worth
placing the /PAE in the boot.ini so there is no mistaking. If it happens to
be there already so be it but at least someone went through the exercise to
ensure it was set. I am almost 100% sure the /3GB is a manual option.
Andrew J. Kelly SQL MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:eF3yxxN9EHA.2180@.TK2MSFTNGP12.phx.gbl...
> Andrew,
> I may have found the answer in KB 838765. It mentions under point 6 of
> Workaround
> Note On a computer that is running Windows Server 2003 the PAE
> specification
> is automatically turned on if the computer is configured to use hot-add
> memory devices.
> Not sure how I can see if the option is set.
> Chris
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:unegDGB9EHA.3416@.TK2MSFTNGP09.phx.gbl...
> what
> that
> I
> would
> for
>|||This is a good one!
Here are two registry keys that you can use to assist you:
HKLM\SYSTEM\CurrentControlSet\Control\Sy
stemStartOptions, will tell you
which BOOT.INI configuration was choosen as the current startup.
HKLM\SYSTEM\CurrentControlSet\Control\Se
ssion Manager\Memory
Management\PhysicalAddressExtensions, will tell you whether or not the PAE
has been enabled for the current startup.
Now, as to your question regarding SQL Server configuration and Win2K3, /3GB
is still required, but there is a new option, /USERVA that will allow you
more granularity of control, BETWEEN 2GB and 3GB, but it REQUIRES the /3GB
to also be present.
/PAE will only assist you with memory above 4GB. All it does is tell the
kernel to use a 36-bit address space, which would give you the ability to
address UP TO 64GB, instead of the default 32-bit address space, which will
allow you to address up to 4GB. Clearly, a 32-bit address is just a subset
of a 36-bit; so, using a 36-bit address space make no sense unless you
actually use the 33rd bit or higher.
If you are using SQL Server Standard Edition, SS will never create a Buffer
Pool larger than 2 GB, period. However, as I have had this conversation
with those here before, SS also uses another memory segment know as MEM TO
LEAVE, which is everything above the 2 GB limit but less than the USER MODE
address space, minus 512MB x Worker Threads, minus -g startup parameter. UM
will be up to 2GB if you have not enabled the /3GB startup option.
So, for SS SE, with the /3GB option enabled and no use of /USERVA, there
will be a 3GB VIRTUAL UM address space. SS SE will create a Buffer Pool of
2GB, maximum, but MEM TO LEAVE will be around 1GB - 384MB. If you have
sufficient physical ram, then most of this will be real memory, but there
will always be some swap space usage.
Now, for Enterprise Edition. What is different here is the ability to use
the AWE features, but also, the real Buffer Pool can also be extended to the
full UM address space. So, with between 2GB and 4GB of physical memory, you
have two options. You can leave AWE disabled, but extend the real Buffer
Pool up to 3GB, or, you can enable AWE, use up to 3GB for the real Buffer
Pool, minus MEM TO LEAVE, and then use the remainder, up to 1GB, of AWE
address space.
With more than 4GB, then you MUST use PAE, whether or not Win2K3 enables
this for you or not, use the registry settings to determine if it was
detected, but AWE will require PAE to make use of any address space above
4GB. In fact, the OS and SS will not even recognize memory greater than 4GB
even exists without PAE enabled.
Hope this helps.
Sincerely,
Anthony Thomas
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:Oh%23rZCP9EHA.3236@.TK2MSFTNGP15.phx.gbl...
I was pretty sure this was the case although I don't recall ever seeing the
condition of Hot Add memory devices. In either case I think it is worth
placing the /PAE in the boot.ini so there is no mistaking. If it happens to
be there already so be it but at least someone went through the exercise to
ensure it was set. I am almost 100% sure the /3GB is a manual option.
Andrew J. Kelly SQL MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:eF3yxxN9EHA.2180@.TK2MSFTNGP12.phx.gbl...
> Andrew,
> I may have found the answer in KB 838765. It mentions under point 6 of
> Workaround
> Note On a computer that is running Windows Server 2003 the PAE
> specification
> is automatically turned on if the computer is configured to use hot-add
> memory devices.
> Not sure how I can see if the option is set.
> Chris
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:unegDGB9EHA.3416@.TK2MSFTNGP09.phx.gbl...
> what
> that
> I
> would
> for
>
Clustered W2K3 Server Memory
Hi,
We have a W2K3 cluster with 3.6Gb memory on each of the 2 servers running
SQL2000 SP3A. We have the /PAE switch on in the boot.ini files on both
nodes. Is SQL2000 able to use more than 2Gb of memory, with this setting, or
do we need the /3GB switch as well with maybe a /USERRVA setting?
Thanks
Chris Wood
Alberta Department of Energy
CANADA/PAE will only be useful if you have over 4Gb Memory . . unfortunately this
switch is redundant is this situation given your memory configuration.
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:ez6Nyiq8EHA.2060@.TK2MSFTNGP10.phx.gbl...
> Hi,
> We have a W2K3 cluster with 3.6Gb memory on each of the 2 servers running
> SQL2000 SP3A. We have the /PAE switch on in the boot.ini files on both
> nodes. Is SQL2000 able to use more than 2Gb of memory, with this setting,
or
> do we need the /3GB switch as well with maybe a /USERRVA setting?
> Thanks
> Chris Wood
> Alberta Department of Energy
> CANADA
>|||Yes the /3GB would be required if you wanted to use more than 2GB for SQL
Server. The /PAE is not used until you have > 4GB.
--
Andrew J. Kelly SQL MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:ez6Nyiq8EHA.2060@.TK2MSFTNGP10.phx.gbl...
> Hi,
> We have a W2K3 cluster with 3.6Gb memory on each of the 2 servers running
> SQL2000 SP3A. We have the /PAE switch on in the boot.ini files on both
> nodes. Is SQL2000 able to use more than 2Gb of memory, with this setting,
> or
> do we need the /3GB switch as well with maybe a /USERRVA setting?
> Thanks
> Chris Wood
> Alberta Department of Energy
> CANADA
>|||Andrew,
Just want to make sure of this as some of our Windows people think that W2K3
is different than W2K for using /3Gb switch.
I have reviewed a number of KB article and it is as clear as mud but I
believe that the /3Gb switch works the same way as in W2K and we would need
it in Boot.Ini for SQL to use more than 2Gb.
Thanks
Chris
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:ufFb8es8EHA.1392@.tk2msftngp13.phx.gbl...
> Yes the /3GB would be required if you wanted to use more than 2GB for SQL
> Server. The /PAE is not used until you have > 4GB.
> --
> Andrew J. Kelly SQL MVP
>
> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
> news:ez6Nyiq8EHA.2060@.TK2MSFTNGP10.phx.gbl...
> > Hi,
> >
> > We have a W2K3 cluster with 3.6Gb memory on each of the 2 servers
running
> > SQL2000 SP3A. We have the /PAE switch on in the boot.ini files on both
> > nodes. Is SQL2000 able to use more than 2Gb of memory, with this
setting,
> > or
> > do we need the /3GB switch as well with maybe a /USERRVA setting?
> >
> > Thanks
> >
> > Chris Wood
> > Alberta Department of Energy
> > CANADA
> >
> >
>|||I am actually having a brain fart<g> at the moment as I can't recall what I
want to answer you properly. There is something about Win2K3 that it does
automatically but I think it is the setting of the /PAE switch and not /3GB.
I believe the /3GB is still required to be set manually.
--
Andrew J. Kelly SQL MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:uF$n$w08EHA.3700@.tk2msftngp13.phx.gbl...
> Andrew,
> Just want to make sure of this as some of our Windows people think that
> W2K3
> is different than W2K for using /3Gb switch.
> I have reviewed a number of KB article and it is as clear as mud but I
> believe that the /3Gb switch works the same way as in W2K and we would
> need
> it in Boot.Ini for SQL to use more than 2Gb.
> Thanks
> Chris
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:ufFb8es8EHA.1392@.tk2msftngp13.phx.gbl...
>> Yes the /3GB would be required if you wanted to use more than 2GB for SQL
>> Server. The /PAE is not used until you have > 4GB.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
>> news:ez6Nyiq8EHA.2060@.TK2MSFTNGP10.phx.gbl...
>> > Hi,
>> >
>> > We have a W2K3 cluster with 3.6Gb memory on each of the 2 servers
> running
>> > SQL2000 SP3A. We have the /PAE switch on in the boot.ini files on both
>> > nodes. Is SQL2000 able to use more than 2Gb of memory, with this
> setting,
>> > or
>> > do we need the /3GB switch as well with maybe a /USERRVA setting?
>> >
>> > Thanks
>> >
>> > Chris Wood
>> > Alberta Department of Energy
>> > CANADA
>> >
>> >
>>
>|||Andrew,
If you can remember that would be great. I still have to convince one
analyst that we need the /3Gb switch and not the /PAE switch set.
Thanks
Chris
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eAxdW618EHA.1400@.TK2MSFTNGP11.phx.gbl...
> I am actually having a brain fart<g> at the moment as I can't recall what
I
> want to answer you properly. There is something about Win2K3 that it does
> automatically but I think it is the setting of the /PAE switch and not
/3GB.
> I believe the /3GB is still required to be set manually.
> --
> Andrew J. Kelly SQL MVP
>
> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
> news:uF$n$w08EHA.3700@.tk2msftngp13.phx.gbl...
> > Andrew,
> >
> > Just want to make sure of this as some of our Windows people think that
> > W2K3
> > is different than W2K for using /3Gb switch.
> >
> > I have reviewed a number of KB article and it is as clear as mud but I
> > believe that the /3Gb switch works the same way as in W2K and we would
> > need
> > it in Boot.Ini for SQL to use more than 2Gb.
> >
> > Thanks
> >
> > Chris
> >
> > "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> > news:ufFb8es8EHA.1392@.tk2msftngp13.phx.gbl...
> >> Yes the /3GB would be required if you wanted to use more than 2GB for
SQL
> >> Server. The /PAE is not used until you have > 4GB.
> >>
> >> --
> >> Andrew J. Kelly SQL MVP
> >>
> >>
> >> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
> >> news:ez6Nyiq8EHA.2060@.TK2MSFTNGP10.phx.gbl...
> >> > Hi,
> >> >
> >> > We have a W2K3 cluster with 3.6Gb memory on each of the 2 servers
> > running
> >> > SQL2000 SP3A. We have the /PAE switch on in the boot.ini files on
both
> >> > nodes. Is SQL2000 able to use more than 2Gb of memory, with this
> > setting,
> >> > or
> >> > do we need the /3GB switch as well with maybe a /USERRVA setting?
> >> >
> >> > Thanks
> >> >
> >> > Chris Wood
> >> > Alberta Department of Energy
> >> > CANADA
> >> >
> >> >
> >>
> >>
> >
> >
>|||Well if they try it without the /3GB and it doesn't give you more than 2GB
it obviously wont work<g>. I will see if I can dig that up.
Andrew J. Kelly SQL MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:%23P58gmA9EHA.3236@.TK2MSFTNGP15.phx.gbl...
> Andrew,
> If you can remember that would be great. I still have to convince one
> analyst that we need the /3Gb switch and not the /PAE switch set.
> Thanks
> Chris
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:eAxdW618EHA.1400@.TK2MSFTNGP11.phx.gbl...
>> I am actually having a brain fart<g> at the moment as I can't recall what
> I
>> want to answer you properly. There is something about Win2K3 that it
>> does
>> automatically but I think it is the setting of the /PAE switch and not
> /3GB.
>> I believe the /3GB is still required to be set manually.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
>> news:uF$n$w08EHA.3700@.tk2msftngp13.phx.gbl...
>> > Andrew,
>> >
>> > Just want to make sure of this as some of our Windows people think that
>> > W2K3
>> > is different than W2K for using /3Gb switch.
>> >
>> > I have reviewed a number of KB article and it is as clear as mud but I
>> > believe that the /3Gb switch works the same way as in W2K and we would
>> > need
>> > it in Boot.Ini for SQL to use more than 2Gb.
>> >
>> > Thanks
>> >
>> > Chris
>> >
>> > "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
>> > news:ufFb8es8EHA.1392@.tk2msftngp13.phx.gbl...
>> >> Yes the /3GB would be required if you wanted to use more than 2GB for
> SQL
>> >> Server. The /PAE is not used until you have > 4GB.
>> >>
>> >> --
>> >> Andrew J. Kelly SQL MVP
>> >>
>> >>
>> >> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
>> >> news:ez6Nyiq8EHA.2060@.TK2MSFTNGP10.phx.gbl...
>> >> > Hi,
>> >> >
>> >> > We have a W2K3 cluster with 3.6Gb memory on each of the 2 servers
>> > running
>> >> > SQL2000 SP3A. We have the /PAE switch on in the boot.ini files on
> both
>> >> > nodes. Is SQL2000 able to use more than 2Gb of memory, with this
>> > setting,
>> >> > or
>> >> > do we need the /3GB switch as well with maybe a /USERRVA setting?
>> >> >
>> >> > Thanks
>> >> >
>> >> > Chris Wood
>> >> > Alberta Department of Energy
>> >> > CANADA
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>>
>|||Andrew,
I may have found the answer in KB 838765. It mentions under point 6 of
Workaround
Note On a computer that is running Windows Server 2003 the PAE specification
is automatically turned on if the computer is configured to use hot-add
memory devices.
Not sure how I can see if the option is set.
Chris
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:unegDGB9EHA.3416@.TK2MSFTNGP09.phx.gbl...
> Well if they try it without the /3GB and it doesn't give you more than 2GB
> it obviously wont work<g>. I will see if I can dig that up.
>
> --
> Andrew J. Kelly SQL MVP
>
> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
> news:%23P58gmA9EHA.3236@.TK2MSFTNGP15.phx.gbl...
> > Andrew,
> >
> > If you can remember that would be great. I still have to convince one
> > analyst that we need the /3Gb switch and not the /PAE switch set.
> >
> > Thanks
> >
> > Chris
> >
> > "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> > news:eAxdW618EHA.1400@.TK2MSFTNGP11.phx.gbl...
> >> I am actually having a brain fart<g> at the moment as I can't recall
what
> > I
> >> want to answer you properly. There is something about Win2K3 that it
> >> does
> >> automatically but I think it is the setting of the /PAE switch and not
> > /3GB.
> >> I believe the /3GB is still required to be set manually.
> >>
> >> --
> >> Andrew J. Kelly SQL MVP
> >>
> >>
> >> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
> >> news:uF$n$w08EHA.3700@.tk2msftngp13.phx.gbl...
> >> > Andrew,
> >> >
> >> > Just want to make sure of this as some of our Windows people think
that
> >> > W2K3
> >> > is different than W2K for using /3Gb switch.
> >> >
> >> > I have reviewed a number of KB article and it is as clear as mud but
I
> >> > believe that the /3Gb switch works the same way as in W2K and we
would
> >> > need
> >> > it in Boot.Ini for SQL to use more than 2Gb.
> >> >
> >> > Thanks
> >> >
> >> > Chris
> >> >
> >> > "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> >> > news:ufFb8es8EHA.1392@.tk2msftngp13.phx.gbl...
> >> >> Yes the /3GB would be required if you wanted to use more than 2GB
for
> > SQL
> >> >> Server. The /PAE is not used until you have > 4GB.
> >> >>
> >> >> --
> >> >> Andrew J. Kelly SQL MVP
> >> >>
> >> >>
> >> >> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
> >> >> news:ez6Nyiq8EHA.2060@.TK2MSFTNGP10.phx.gbl...
> >> >> > Hi,
> >> >> >
> >> >> > We have a W2K3 cluster with 3.6Gb memory on each of the 2 servers
> >> > running
> >> >> > SQL2000 SP3A. We have the /PAE switch on in the boot.ini files on
> > both
> >> >> > nodes. Is SQL2000 able to use more than 2Gb of memory, with this
> >> > setting,
> >> >> > or
> >> >> > do we need the /3GB switch as well with maybe a /USERRVA setting?
> >> >> >
> >> >> > Thanks
> >> >> >
> >> >> > Chris Wood
> >> >> > Alberta Department of Energy
> >> >> > CANADA
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >
> >
>|||I was pretty sure this was the case although I don't recall ever seeing the
condition of Hot Add memory devices. In either case I think it is worth
placing the /PAE in the boot.ini so there is no mistaking. If it happens to
be there already so be it but at least someone went through the exercise to
ensure it was set. I am almost 100% sure the /3GB is a manual option.
--
Andrew J. Kelly SQL MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:eF3yxxN9EHA.2180@.TK2MSFTNGP12.phx.gbl...
> Andrew,
> I may have found the answer in KB 838765. It mentions under point 6 of
> Workaround
> Note On a computer that is running Windows Server 2003 the PAE
> specification
> is automatically turned on if the computer is configured to use hot-add
> memory devices.
> Not sure how I can see if the option is set.
> Chris
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:unegDGB9EHA.3416@.TK2MSFTNGP09.phx.gbl...
>> Well if they try it without the /3GB and it doesn't give you more than
>> 2GB
>> it obviously wont work<g>. I will see if I can dig that up.
>>
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
>> news:%23P58gmA9EHA.3236@.TK2MSFTNGP15.phx.gbl...
>> > Andrew,
>> >
>> > If you can remember that would be great. I still have to convince one
>> > analyst that we need the /3Gb switch and not the /PAE switch set.
>> >
>> > Thanks
>> >
>> > Chris
>> >
>> > "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
>> > news:eAxdW618EHA.1400@.TK2MSFTNGP11.phx.gbl...
>> >> I am actually having a brain fart<g> at the moment as I can't recall
> what
>> > I
>> >> want to answer you properly. There is something about Win2K3 that it
>> >> does
>> >> automatically but I think it is the setting of the /PAE switch and not
>> > /3GB.
>> >> I believe the /3GB is still required to be set manually.
>> >>
>> >> --
>> >> Andrew J. Kelly SQL MVP
>> >>
>> >>
>> >> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
>> >> news:uF$n$w08EHA.3700@.tk2msftngp13.phx.gbl...
>> >> > Andrew,
>> >> >
>> >> > Just want to make sure of this as some of our Windows people think
> that
>> >> > W2K3
>> >> > is different than W2K for using /3Gb switch.
>> >> >
>> >> > I have reviewed a number of KB article and it is as clear as mud but
> I
>> >> > believe that the /3Gb switch works the same way as in W2K and we
> would
>> >> > need
>> >> > it in Boot.Ini for SQL to use more than 2Gb.
>> >> >
>> >> > Thanks
>> >> >
>> >> > Chris
>> >> >
>> >> > "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
>> >> > news:ufFb8es8EHA.1392@.tk2msftngp13.phx.gbl...
>> >> >> Yes the /3GB would be required if you wanted to use more than 2GB
> for
>> > SQL
>> >> >> Server. The /PAE is not used until you have > 4GB.
>> >> >>
>> >> >> --
>> >> >> Andrew J. Kelly SQL MVP
>> >> >>
>> >> >>
>> >> >> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
>> >> >> news:ez6Nyiq8EHA.2060@.TK2MSFTNGP10.phx.gbl...
>> >> >> > Hi,
>> >> >> >
>> >> >> > We have a W2K3 cluster with 3.6Gb memory on each of the 2 servers
>> >> > running
>> >> >> > SQL2000 SP3A. We have the /PAE switch on in the boot.ini files on
>> > both
>> >> >> > nodes. Is SQL2000 able to use more than 2Gb of memory, with this
>> >> > setting,
>> >> >> > or
>> >> >> > do we need the /3GB switch as well with maybe a /USERRVA setting?
>> >> >> >
>> >> >> > Thanks
>> >> >> >
>> >> >> > Chris Wood
>> >> >> > Alberta Department of Energy
>> >> >> > CANADA
>> >> >> >
>> >> >> >
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>>
>|||This is a good one!
Here are two registry keys that you can use to assist you:
HKLM\SYSTEM\CurrentControlSet\Control\SystemStartOptions, will tell you
which BOOT.INI configuration was choosen as the current startup.
HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory
Management\PhysicalAddressExtensions, will tell you whether or not the PAE
has been enabled for the current startup.
Now, as to your question regarding SQL Server configuration and Win2K3, /3GB
is still required, but there is a new option, /USERVA that will allow you
more granularity of control, BETWEEN 2GB and 3GB, but it REQUIRES the /3GB
to also be present.
/PAE will only assist you with memory above 4GB. All it does is tell the
kernel to use a 36-bit address space, which would give you the ability to
address UP TO 64GB, instead of the default 32-bit address space, which will
allow you to address up to 4GB. Clearly, a 32-bit address is just a subset
of a 36-bit; so, using a 36-bit address space make no sense unless you
actually use the 33rd bit or higher.
If you are using SQL Server Standard Edition, SS will never create a Buffer
Pool larger than 2 GB, period. However, as I have had this conversation
with those here before, SS also uses another memory segment know as MEM TO
LEAVE, which is everything above the 2 GB limit but less than the USER MODE
address space, minus 512MB x Worker Threads, minus -g startup parameter. UM
will be up to 2GB if you have not enabled the /3GB startup option.
So, for SS SE, with the /3GB option enabled and no use of /USERVA, there
will be a 3GB VIRTUAL UM address space. SS SE will create a Buffer Pool of
2GB, maximum, but MEM TO LEAVE will be around 1GB - 384MB. If you have
sufficient physical ram, then most of this will be real memory, but there
will always be some swap space usage.
Now, for Enterprise Edition. What is different here is the ability to use
the AWE features, but also, the real Buffer Pool can also be extended to the
full UM address space. So, with between 2GB and 4GB of physical memory, you
have two options. You can leave AWE disabled, but extend the real Buffer
Pool up to 3GB, or, you can enable AWE, use up to 3GB for the real Buffer
Pool, minus MEM TO LEAVE, and then use the remainder, up to 1GB, of AWE
address space.
With more than 4GB, then you MUST use PAE, whether or not Win2K3 enables
this for you or not, use the registry settings to determine if it was
detected, but AWE will require PAE to make use of any address space above
4GB. In fact, the OS and SS will not even recognize memory greater than 4GB
even exists without PAE enabled.
Hope this helps.
Sincerely,
Anthony Thomas
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:Oh%23rZCP9EHA.3236@.TK2MSFTNGP15.phx.gbl...
I was pretty sure this was the case although I don't recall ever seeing the
condition of Hot Add memory devices. In either case I think it is worth
placing the /PAE in the boot.ini so there is no mistaking. If it happens to
be there already so be it but at least someone went through the exercise to
ensure it was set. I am almost 100% sure the /3GB is a manual option.
--
Andrew J. Kelly SQL MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:eF3yxxN9EHA.2180@.TK2MSFTNGP12.phx.gbl...
> Andrew,
> I may have found the answer in KB 838765. It mentions under point 6 of
> Workaround
> Note On a computer that is running Windows Server 2003 the PAE
> specification
> is automatically turned on if the computer is configured to use hot-add
> memory devices.
> Not sure how I can see if the option is set.
> Chris
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:unegDGB9EHA.3416@.TK2MSFTNGP09.phx.gbl...
>> Well if they try it without the /3GB and it doesn't give you more than
>> 2GB
>> it obviously wont work<g>. I will see if I can dig that up.
>>
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
>> news:%23P58gmA9EHA.3236@.TK2MSFTNGP15.phx.gbl...
>> > Andrew,
>> >
>> > If you can remember that would be great. I still have to convince one
>> > analyst that we need the /3Gb switch and not the /PAE switch set.
>> >
>> > Thanks
>> >
>> > Chris
>> >
>> > "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
>> > news:eAxdW618EHA.1400@.TK2MSFTNGP11.phx.gbl...
>> >> I am actually having a brain fart<g> at the moment as I can't recall
> what
>> > I
>> >> want to answer you properly. There is something about Win2K3 that it
>> >> does
>> >> automatically but I think it is the setting of the /PAE switch and not
>> > /3GB.
>> >> I believe the /3GB is still required to be set manually.
>> >>
>> >> --
>> >> Andrew J. Kelly SQL MVP
>> >>
>> >>
>> >> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
>> >> news:uF$n$w08EHA.3700@.tk2msftngp13.phx.gbl...
>> >> > Andrew,
>> >> >
>> >> > Just want to make sure of this as some of our Windows people think
> that
>> >> > W2K3
>> >> > is different than W2K for using /3Gb switch.
>> >> >
>> >> > I have reviewed a number of KB article and it is as clear as mud but
> I
>> >> > believe that the /3Gb switch works the same way as in W2K and we
> would
>> >> > need
>> >> > it in Boot.Ini for SQL to use more than 2Gb.
>> >> >
>> >> > Thanks
>> >> >
>> >> > Chris
>> >> >
>> >> > "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
>> >> > news:ufFb8es8EHA.1392@.tk2msftngp13.phx.gbl...
>> >> >> Yes the /3GB would be required if you wanted to use more than 2GB
> for
>> > SQL
>> >> >> Server. The /PAE is not used until you have > 4GB.
>> >> >>
>> >> >> --
>> >> >> Andrew J. Kelly SQL MVP
>> >> >>
>> >> >>
>> >> >> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
>> >> >> news:ez6Nyiq8EHA.2060@.TK2MSFTNGP10.phx.gbl...
>> >> >> > Hi,
>> >> >> >
>> >> >> > We have a W2K3 cluster with 3.6Gb memory on each of the 2 servers
>> >> > running
>> >> >> > SQL2000 SP3A. We have the /PAE switch on in the boot.ini files on
>> > both
>> >> >> > nodes. Is SQL2000 able to use more than 2Gb of memory, with this
>> >> > setting,
>> >> >> > or
>> >> >> > do we need the /3GB switch as well with maybe a /USERRVA setting?
>> >> >> >
>> >> >> > Thanks
>> >> >> >
>> >> >> > Chris Wood
>> >> >> > Alberta Department of Energy
>> >> >> > CANADA
>> >> >> >
>> >> >> >
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>>
>
We have a W2K3 cluster with 3.6Gb memory on each of the 2 servers running
SQL2000 SP3A. We have the /PAE switch on in the boot.ini files on both
nodes. Is SQL2000 able to use more than 2Gb of memory, with this setting, or
do we need the /3GB switch as well with maybe a /USERRVA setting?
Thanks
Chris Wood
Alberta Department of Energy
CANADA/PAE will only be useful if you have over 4Gb Memory . . unfortunately this
switch is redundant is this situation given your memory configuration.
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:ez6Nyiq8EHA.2060@.TK2MSFTNGP10.phx.gbl...
> Hi,
> We have a W2K3 cluster with 3.6Gb memory on each of the 2 servers running
> SQL2000 SP3A. We have the /PAE switch on in the boot.ini files on both
> nodes. Is SQL2000 able to use more than 2Gb of memory, with this setting,
or
> do we need the /3GB switch as well with maybe a /USERRVA setting?
> Thanks
> Chris Wood
> Alberta Department of Energy
> CANADA
>|||Yes the /3GB would be required if you wanted to use more than 2GB for SQL
Server. The /PAE is not used until you have > 4GB.
--
Andrew J. Kelly SQL MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:ez6Nyiq8EHA.2060@.TK2MSFTNGP10.phx.gbl...
> Hi,
> We have a W2K3 cluster with 3.6Gb memory on each of the 2 servers running
> SQL2000 SP3A. We have the /PAE switch on in the boot.ini files on both
> nodes. Is SQL2000 able to use more than 2Gb of memory, with this setting,
> or
> do we need the /3GB switch as well with maybe a /USERRVA setting?
> Thanks
> Chris Wood
> Alberta Department of Energy
> CANADA
>|||Andrew,
Just want to make sure of this as some of our Windows people think that W2K3
is different than W2K for using /3Gb switch.
I have reviewed a number of KB article and it is as clear as mud but I
believe that the /3Gb switch works the same way as in W2K and we would need
it in Boot.Ini for SQL to use more than 2Gb.
Thanks
Chris
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:ufFb8es8EHA.1392@.tk2msftngp13.phx.gbl...
> Yes the /3GB would be required if you wanted to use more than 2GB for SQL
> Server. The /PAE is not used until you have > 4GB.
> --
> Andrew J. Kelly SQL MVP
>
> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
> news:ez6Nyiq8EHA.2060@.TK2MSFTNGP10.phx.gbl...
> > Hi,
> >
> > We have a W2K3 cluster with 3.6Gb memory on each of the 2 servers
running
> > SQL2000 SP3A. We have the /PAE switch on in the boot.ini files on both
> > nodes. Is SQL2000 able to use more than 2Gb of memory, with this
setting,
> > or
> > do we need the /3GB switch as well with maybe a /USERRVA setting?
> >
> > Thanks
> >
> > Chris Wood
> > Alberta Department of Energy
> > CANADA
> >
> >
>|||I am actually having a brain fart<g> at the moment as I can't recall what I
want to answer you properly. There is something about Win2K3 that it does
automatically but I think it is the setting of the /PAE switch and not /3GB.
I believe the /3GB is still required to be set manually.
--
Andrew J. Kelly SQL MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:uF$n$w08EHA.3700@.tk2msftngp13.phx.gbl...
> Andrew,
> Just want to make sure of this as some of our Windows people think that
> W2K3
> is different than W2K for using /3Gb switch.
> I have reviewed a number of KB article and it is as clear as mud but I
> believe that the /3Gb switch works the same way as in W2K and we would
> need
> it in Boot.Ini for SQL to use more than 2Gb.
> Thanks
> Chris
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:ufFb8es8EHA.1392@.tk2msftngp13.phx.gbl...
>> Yes the /3GB would be required if you wanted to use more than 2GB for SQL
>> Server. The /PAE is not used until you have > 4GB.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
>> news:ez6Nyiq8EHA.2060@.TK2MSFTNGP10.phx.gbl...
>> > Hi,
>> >
>> > We have a W2K3 cluster with 3.6Gb memory on each of the 2 servers
> running
>> > SQL2000 SP3A. We have the /PAE switch on in the boot.ini files on both
>> > nodes. Is SQL2000 able to use more than 2Gb of memory, with this
> setting,
>> > or
>> > do we need the /3GB switch as well with maybe a /USERRVA setting?
>> >
>> > Thanks
>> >
>> > Chris Wood
>> > Alberta Department of Energy
>> > CANADA
>> >
>> >
>>
>|||Andrew,
If you can remember that would be great. I still have to convince one
analyst that we need the /3Gb switch and not the /PAE switch set.
Thanks
Chris
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eAxdW618EHA.1400@.TK2MSFTNGP11.phx.gbl...
> I am actually having a brain fart<g> at the moment as I can't recall what
I
> want to answer you properly. There is something about Win2K3 that it does
> automatically but I think it is the setting of the /PAE switch and not
/3GB.
> I believe the /3GB is still required to be set manually.
> --
> Andrew J. Kelly SQL MVP
>
> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
> news:uF$n$w08EHA.3700@.tk2msftngp13.phx.gbl...
> > Andrew,
> >
> > Just want to make sure of this as some of our Windows people think that
> > W2K3
> > is different than W2K for using /3Gb switch.
> >
> > I have reviewed a number of KB article and it is as clear as mud but I
> > believe that the /3Gb switch works the same way as in W2K and we would
> > need
> > it in Boot.Ini for SQL to use more than 2Gb.
> >
> > Thanks
> >
> > Chris
> >
> > "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> > news:ufFb8es8EHA.1392@.tk2msftngp13.phx.gbl...
> >> Yes the /3GB would be required if you wanted to use more than 2GB for
SQL
> >> Server. The /PAE is not used until you have > 4GB.
> >>
> >> --
> >> Andrew J. Kelly SQL MVP
> >>
> >>
> >> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
> >> news:ez6Nyiq8EHA.2060@.TK2MSFTNGP10.phx.gbl...
> >> > Hi,
> >> >
> >> > We have a W2K3 cluster with 3.6Gb memory on each of the 2 servers
> > running
> >> > SQL2000 SP3A. We have the /PAE switch on in the boot.ini files on
both
> >> > nodes. Is SQL2000 able to use more than 2Gb of memory, with this
> > setting,
> >> > or
> >> > do we need the /3GB switch as well with maybe a /USERRVA setting?
> >> >
> >> > Thanks
> >> >
> >> > Chris Wood
> >> > Alberta Department of Energy
> >> > CANADA
> >> >
> >> >
> >>
> >>
> >
> >
>|||Well if they try it without the /3GB and it doesn't give you more than 2GB
it obviously wont work<g>. I will see if I can dig that up.
Andrew J. Kelly SQL MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:%23P58gmA9EHA.3236@.TK2MSFTNGP15.phx.gbl...
> Andrew,
> If you can remember that would be great. I still have to convince one
> analyst that we need the /3Gb switch and not the /PAE switch set.
> Thanks
> Chris
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:eAxdW618EHA.1400@.TK2MSFTNGP11.phx.gbl...
>> I am actually having a brain fart<g> at the moment as I can't recall what
> I
>> want to answer you properly. There is something about Win2K3 that it
>> does
>> automatically but I think it is the setting of the /PAE switch and not
> /3GB.
>> I believe the /3GB is still required to be set manually.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
>> news:uF$n$w08EHA.3700@.tk2msftngp13.phx.gbl...
>> > Andrew,
>> >
>> > Just want to make sure of this as some of our Windows people think that
>> > W2K3
>> > is different than W2K for using /3Gb switch.
>> >
>> > I have reviewed a number of KB article and it is as clear as mud but I
>> > believe that the /3Gb switch works the same way as in W2K and we would
>> > need
>> > it in Boot.Ini for SQL to use more than 2Gb.
>> >
>> > Thanks
>> >
>> > Chris
>> >
>> > "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
>> > news:ufFb8es8EHA.1392@.tk2msftngp13.phx.gbl...
>> >> Yes the /3GB would be required if you wanted to use more than 2GB for
> SQL
>> >> Server. The /PAE is not used until you have > 4GB.
>> >>
>> >> --
>> >> Andrew J. Kelly SQL MVP
>> >>
>> >>
>> >> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
>> >> news:ez6Nyiq8EHA.2060@.TK2MSFTNGP10.phx.gbl...
>> >> > Hi,
>> >> >
>> >> > We have a W2K3 cluster with 3.6Gb memory on each of the 2 servers
>> > running
>> >> > SQL2000 SP3A. We have the /PAE switch on in the boot.ini files on
> both
>> >> > nodes. Is SQL2000 able to use more than 2Gb of memory, with this
>> > setting,
>> >> > or
>> >> > do we need the /3GB switch as well with maybe a /USERRVA setting?
>> >> >
>> >> > Thanks
>> >> >
>> >> > Chris Wood
>> >> > Alberta Department of Energy
>> >> > CANADA
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>>
>|||Andrew,
I may have found the answer in KB 838765. It mentions under point 6 of
Workaround
Note On a computer that is running Windows Server 2003 the PAE specification
is automatically turned on if the computer is configured to use hot-add
memory devices.
Not sure how I can see if the option is set.
Chris
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:unegDGB9EHA.3416@.TK2MSFTNGP09.phx.gbl...
> Well if they try it without the /3GB and it doesn't give you more than 2GB
> it obviously wont work<g>. I will see if I can dig that up.
>
> --
> Andrew J. Kelly SQL MVP
>
> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
> news:%23P58gmA9EHA.3236@.TK2MSFTNGP15.phx.gbl...
> > Andrew,
> >
> > If you can remember that would be great. I still have to convince one
> > analyst that we need the /3Gb switch and not the /PAE switch set.
> >
> > Thanks
> >
> > Chris
> >
> > "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> > news:eAxdW618EHA.1400@.TK2MSFTNGP11.phx.gbl...
> >> I am actually having a brain fart<g> at the moment as I can't recall
what
> > I
> >> want to answer you properly. There is something about Win2K3 that it
> >> does
> >> automatically but I think it is the setting of the /PAE switch and not
> > /3GB.
> >> I believe the /3GB is still required to be set manually.
> >>
> >> --
> >> Andrew J. Kelly SQL MVP
> >>
> >>
> >> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
> >> news:uF$n$w08EHA.3700@.tk2msftngp13.phx.gbl...
> >> > Andrew,
> >> >
> >> > Just want to make sure of this as some of our Windows people think
that
> >> > W2K3
> >> > is different than W2K for using /3Gb switch.
> >> >
> >> > I have reviewed a number of KB article and it is as clear as mud but
I
> >> > believe that the /3Gb switch works the same way as in W2K and we
would
> >> > need
> >> > it in Boot.Ini for SQL to use more than 2Gb.
> >> >
> >> > Thanks
> >> >
> >> > Chris
> >> >
> >> > "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> >> > news:ufFb8es8EHA.1392@.tk2msftngp13.phx.gbl...
> >> >> Yes the /3GB would be required if you wanted to use more than 2GB
for
> > SQL
> >> >> Server. The /PAE is not used until you have > 4GB.
> >> >>
> >> >> --
> >> >> Andrew J. Kelly SQL MVP
> >> >>
> >> >>
> >> >> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
> >> >> news:ez6Nyiq8EHA.2060@.TK2MSFTNGP10.phx.gbl...
> >> >> > Hi,
> >> >> >
> >> >> > We have a W2K3 cluster with 3.6Gb memory on each of the 2 servers
> >> > running
> >> >> > SQL2000 SP3A. We have the /PAE switch on in the boot.ini files on
> > both
> >> >> > nodes. Is SQL2000 able to use more than 2Gb of memory, with this
> >> > setting,
> >> >> > or
> >> >> > do we need the /3GB switch as well with maybe a /USERRVA setting?
> >> >> >
> >> >> > Thanks
> >> >> >
> >> >> > Chris Wood
> >> >> > Alberta Department of Energy
> >> >> > CANADA
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >
> >
>|||I was pretty sure this was the case although I don't recall ever seeing the
condition of Hot Add memory devices. In either case I think it is worth
placing the /PAE in the boot.ini so there is no mistaking. If it happens to
be there already so be it but at least someone went through the exercise to
ensure it was set. I am almost 100% sure the /3GB is a manual option.
--
Andrew J. Kelly SQL MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:eF3yxxN9EHA.2180@.TK2MSFTNGP12.phx.gbl...
> Andrew,
> I may have found the answer in KB 838765. It mentions under point 6 of
> Workaround
> Note On a computer that is running Windows Server 2003 the PAE
> specification
> is automatically turned on if the computer is configured to use hot-add
> memory devices.
> Not sure how I can see if the option is set.
> Chris
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:unegDGB9EHA.3416@.TK2MSFTNGP09.phx.gbl...
>> Well if they try it without the /3GB and it doesn't give you more than
>> 2GB
>> it obviously wont work<g>. I will see if I can dig that up.
>>
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
>> news:%23P58gmA9EHA.3236@.TK2MSFTNGP15.phx.gbl...
>> > Andrew,
>> >
>> > If you can remember that would be great. I still have to convince one
>> > analyst that we need the /3Gb switch and not the /PAE switch set.
>> >
>> > Thanks
>> >
>> > Chris
>> >
>> > "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
>> > news:eAxdW618EHA.1400@.TK2MSFTNGP11.phx.gbl...
>> >> I am actually having a brain fart<g> at the moment as I can't recall
> what
>> > I
>> >> want to answer you properly. There is something about Win2K3 that it
>> >> does
>> >> automatically but I think it is the setting of the /PAE switch and not
>> > /3GB.
>> >> I believe the /3GB is still required to be set manually.
>> >>
>> >> --
>> >> Andrew J. Kelly SQL MVP
>> >>
>> >>
>> >> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
>> >> news:uF$n$w08EHA.3700@.tk2msftngp13.phx.gbl...
>> >> > Andrew,
>> >> >
>> >> > Just want to make sure of this as some of our Windows people think
> that
>> >> > W2K3
>> >> > is different than W2K for using /3Gb switch.
>> >> >
>> >> > I have reviewed a number of KB article and it is as clear as mud but
> I
>> >> > believe that the /3Gb switch works the same way as in W2K and we
> would
>> >> > need
>> >> > it in Boot.Ini for SQL to use more than 2Gb.
>> >> >
>> >> > Thanks
>> >> >
>> >> > Chris
>> >> >
>> >> > "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
>> >> > news:ufFb8es8EHA.1392@.tk2msftngp13.phx.gbl...
>> >> >> Yes the /3GB would be required if you wanted to use more than 2GB
> for
>> > SQL
>> >> >> Server. The /PAE is not used until you have > 4GB.
>> >> >>
>> >> >> --
>> >> >> Andrew J. Kelly SQL MVP
>> >> >>
>> >> >>
>> >> >> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
>> >> >> news:ez6Nyiq8EHA.2060@.TK2MSFTNGP10.phx.gbl...
>> >> >> > Hi,
>> >> >> >
>> >> >> > We have a W2K3 cluster with 3.6Gb memory on each of the 2 servers
>> >> > running
>> >> >> > SQL2000 SP3A. We have the /PAE switch on in the boot.ini files on
>> > both
>> >> >> > nodes. Is SQL2000 able to use more than 2Gb of memory, with this
>> >> > setting,
>> >> >> > or
>> >> >> > do we need the /3GB switch as well with maybe a /USERRVA setting?
>> >> >> >
>> >> >> > Thanks
>> >> >> >
>> >> >> > Chris Wood
>> >> >> > Alberta Department of Energy
>> >> >> > CANADA
>> >> >> >
>> >> >> >
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>>
>|||This is a good one!
Here are two registry keys that you can use to assist you:
HKLM\SYSTEM\CurrentControlSet\Control\SystemStartOptions, will tell you
which BOOT.INI configuration was choosen as the current startup.
HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory
Management\PhysicalAddressExtensions, will tell you whether or not the PAE
has been enabled for the current startup.
Now, as to your question regarding SQL Server configuration and Win2K3, /3GB
is still required, but there is a new option, /USERVA that will allow you
more granularity of control, BETWEEN 2GB and 3GB, but it REQUIRES the /3GB
to also be present.
/PAE will only assist you with memory above 4GB. All it does is tell the
kernel to use a 36-bit address space, which would give you the ability to
address UP TO 64GB, instead of the default 32-bit address space, which will
allow you to address up to 4GB. Clearly, a 32-bit address is just a subset
of a 36-bit; so, using a 36-bit address space make no sense unless you
actually use the 33rd bit or higher.
If you are using SQL Server Standard Edition, SS will never create a Buffer
Pool larger than 2 GB, period. However, as I have had this conversation
with those here before, SS also uses another memory segment know as MEM TO
LEAVE, which is everything above the 2 GB limit but less than the USER MODE
address space, minus 512MB x Worker Threads, minus -g startup parameter. UM
will be up to 2GB if you have not enabled the /3GB startup option.
So, for SS SE, with the /3GB option enabled and no use of /USERVA, there
will be a 3GB VIRTUAL UM address space. SS SE will create a Buffer Pool of
2GB, maximum, but MEM TO LEAVE will be around 1GB - 384MB. If you have
sufficient physical ram, then most of this will be real memory, but there
will always be some swap space usage.
Now, for Enterprise Edition. What is different here is the ability to use
the AWE features, but also, the real Buffer Pool can also be extended to the
full UM address space. So, with between 2GB and 4GB of physical memory, you
have two options. You can leave AWE disabled, but extend the real Buffer
Pool up to 3GB, or, you can enable AWE, use up to 3GB for the real Buffer
Pool, minus MEM TO LEAVE, and then use the remainder, up to 1GB, of AWE
address space.
With more than 4GB, then you MUST use PAE, whether or not Win2K3 enables
this for you or not, use the registry settings to determine if it was
detected, but AWE will require PAE to make use of any address space above
4GB. In fact, the OS and SS will not even recognize memory greater than 4GB
even exists without PAE enabled.
Hope this helps.
Sincerely,
Anthony Thomas
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:Oh%23rZCP9EHA.3236@.TK2MSFTNGP15.phx.gbl...
I was pretty sure this was the case although I don't recall ever seeing the
condition of Hot Add memory devices. In either case I think it is worth
placing the /PAE in the boot.ini so there is no mistaking. If it happens to
be there already so be it but at least someone went through the exercise to
ensure it was set. I am almost 100% sure the /3GB is a manual option.
--
Andrew J. Kelly SQL MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:eF3yxxN9EHA.2180@.TK2MSFTNGP12.phx.gbl...
> Andrew,
> I may have found the answer in KB 838765. It mentions under point 6 of
> Workaround
> Note On a computer that is running Windows Server 2003 the PAE
> specification
> is automatically turned on if the computer is configured to use hot-add
> memory devices.
> Not sure how I can see if the option is set.
> Chris
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:unegDGB9EHA.3416@.TK2MSFTNGP09.phx.gbl...
>> Well if they try it without the /3GB and it doesn't give you more than
>> 2GB
>> it obviously wont work<g>. I will see if I can dig that up.
>>
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
>> news:%23P58gmA9EHA.3236@.TK2MSFTNGP15.phx.gbl...
>> > Andrew,
>> >
>> > If you can remember that would be great. I still have to convince one
>> > analyst that we need the /3Gb switch and not the /PAE switch set.
>> >
>> > Thanks
>> >
>> > Chris
>> >
>> > "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
>> > news:eAxdW618EHA.1400@.TK2MSFTNGP11.phx.gbl...
>> >> I am actually having a brain fart<g> at the moment as I can't recall
> what
>> > I
>> >> want to answer you properly. There is something about Win2K3 that it
>> >> does
>> >> automatically but I think it is the setting of the /PAE switch and not
>> > /3GB.
>> >> I believe the /3GB is still required to be set manually.
>> >>
>> >> --
>> >> Andrew J. Kelly SQL MVP
>> >>
>> >>
>> >> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
>> >> news:uF$n$w08EHA.3700@.tk2msftngp13.phx.gbl...
>> >> > Andrew,
>> >> >
>> >> > Just want to make sure of this as some of our Windows people think
> that
>> >> > W2K3
>> >> > is different than W2K for using /3Gb switch.
>> >> >
>> >> > I have reviewed a number of KB article and it is as clear as mud but
> I
>> >> > believe that the /3Gb switch works the same way as in W2K and we
> would
>> >> > need
>> >> > it in Boot.Ini for SQL to use more than 2Gb.
>> >> >
>> >> > Thanks
>> >> >
>> >> > Chris
>> >> >
>> >> > "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
>> >> > news:ufFb8es8EHA.1392@.tk2msftngp13.phx.gbl...
>> >> >> Yes the /3GB would be required if you wanted to use more than 2GB
> for
>> > SQL
>> >> >> Server. The /PAE is not used until you have > 4GB.
>> >> >>
>> >> >> --
>> >> >> Andrew J. Kelly SQL MVP
>> >> >>
>> >> >>
>> >> >> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
>> >> >> news:ez6Nyiq8EHA.2060@.TK2MSFTNGP10.phx.gbl...
>> >> >> > Hi,
>> >> >> >
>> >> >> > We have a W2K3 cluster with 3.6Gb memory on each of the 2 servers
>> >> > running
>> >> >> > SQL2000 SP3A. We have the /PAE switch on in the boot.ini files on
>> > both
>> >> >> > nodes. Is SQL2000 able to use more than 2Gb of memory, with this
>> >> > setting,
>> >> >> > or
>> >> >> > do we need the /3GB switch as well with maybe a /USERRVA setting?
>> >> >> >
>> >> >> > Thanks
>> >> >> >
>> >> >> > Chris Wood
>> >> >> > Alberta Department of Energy
>> >> >> > CANADA
>> >> >> >
>> >> >> >
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>>
>
Tuesday, February 14, 2012
Clustered SQL 2000
I am currently running a SQL 2000 Ent Server sitting on a MSCS running W2K3 Ent Edition.
One of the nodes is giving me problems, and I suspect that it is due to the build.
I want to evict the offending from the cluster and then rebuild the OS from scratch, and then rejoin the cluster.
My question then is how do I install SQL 2000 Server, up to tha same revision as the existing node, on the newly installed node without overwritting any of the existing data?you should be able to do so just back up your databases system and user
when you reinstall sql server
the advanced options will prompt you for the cluster install.
but as you already know. you will have to update the installation to be as current in version as your existing node.
One of the nodes is giving me problems, and I suspect that it is due to the build.
I want to evict the offending from the cluster and then rebuild the OS from scratch, and then rejoin the cluster.
My question then is how do I install SQL 2000 Server, up to tha same revision as the existing node, on the newly installed node without overwritting any of the existing data?you should be able to do so just back up your databases system and user
when you reinstall sql server
the advanced options will prompt you for the cluster install.
but as you already know. you will have to update the installation to be as current in version as your existing node.
Subscribe to:
Posts (Atom)