If you use the /3GB switch should the memory slider in SQL Enterprise
Manager display up to 3GB or do you set manually and just assume it's
working?
2000 Advanced server and SQL 2000 Enterprise Edition.
Thanks
Paul
Paul,
The maximum value of the slider should show a value of 3-something . (in my
environments it's 3455).
I would suggest not setting a fixed size, always let SQL use as much as
possible.
JP
"Paul Cahill" wrote:
> If you use the /3GB switch should the memory slider in SQL Enterprise
> Manager display up to 3GB or do you set manually and just assume it's
> working?
> 2000 Advanced server and SQL 2000 Enterprise Edition.
> Thanks
> Paul
>
>
|||Thanks JP.
Have you got 4GB Ram and if so are you just using /3GB and not PAE or AWE.
I have exactly 4GB ram. If I use PAE the slider in enterprise manager shows
4GB max. With /3GB I only see 2GB.
I don't want to have the overhead of /PAE and it should not be necessary. Is
there any way to see if /3GB is working (from an NT or SQL)?
Paul
"JP de Jong" <JP de Jong@.discussions.microsoft.com> wrote in message
news:1447D55D-C78C-41E8-87EB-FDF4C0E082D8@.microsoft.com...[vbcol=seagreen]
> Paul,
> The maximum value of the slider should show a value of 3-something . (in
> my
> environments it's 3455).
> I would suggest not setting a fixed size, always let SQL use as much as
> possible.
> JP
> "Paul Cahill" wrote:
|||Paul
Just checked it for you.
We have 4GB RAM in server (Windows 2003Server). In BoOT.INI we have "/3GB
/PAE". (so we do have PAE enabled).
In properties of system (my computer) it says. Physical Address Extensions
enabled. Not sure how to check if /3GB is enabled. You're absolutelt right
that /PAE only is effective when you have more than 4 GB.
/3GB only enables applications to use more virtual memory. I'm not quite
sure if you can find that back in the gui of SQL.
JP
"Paul Cahill" wrote:
> Thanks JP.
> Have you got 4GB Ram and if so are you just using /3GB and not PAE or AWE.
> I have exactly 4GB ram. If I use PAE the slider in enterprise manager shows
> 4GB max. With /3GB I only see 2GB.
> I don't want to have the overhead of /PAE and it should not be necessary. Is
> there any way to see if /3GB is working (from an NT or SQL)?
> Paul
>
> "JP de Jong" <JP de Jong@.discussions.microsoft.com> wrote in message
> news:1447D55D-C78C-41E8-87EB-FDF4C0E082D8@.microsoft.com...
>
>
|||Thanks JP.
Any idea why you have /PAE? I thought there's got to be an overhead for
address translation.
You don't feel like trying something for me......
Paul
"JP de Jong" <JPdeJong@.discussions.microsoft.com> wrote in message
news:45DC15E7-3C0D-4DD0-ACEE-732E9A8504E0@.microsoft.com...[vbcol=seagreen]
> Paul
> Just checked it for you.
> We have 4GB RAM in server (Windows 2003Server). In BoOT.INI we have "/3GB
> /PAE". (so we do have PAE enabled).
> In properties of system (my computer) it says. Physical Address Extensions
> enabled. Not sure how to check if /3GB is enabled. You're absolutelt right
> that /PAE only is effective when you have more than 4 GB.
> /3GB only enables applications to use more virtual memory. I'm not quite
> sure if you can find that back in the gui of SQL.
> JP
> "Paul Cahill" wrote:
Showing posts with label ent. Show all posts
Showing posts with label ent. Show all posts
Thursday, February 16, 2012
4GB Ram /3GB and the memory slider in Ent Manager
If you use the /3GB switch should the memory slider in SQL Enterprise
Manager display up to 3GB or do you set manually and just assume it's
working?
2000 Advanced server and SQL 2000 Enterprise Edition.
Thanks
PaulPaul,
The maximum value of the slider should show a value of 3-something . (in my
environments it's 3455).
I would suggest not setting a fixed size, always let SQL use as much as
possible.
JP
"Paul Cahill" wrote:
> If you use the /3GB switch should the memory slider in SQL Enterprise
> Manager display up to 3GB or do you set manually and just assume it's
> working?
> 2000 Advanced server and SQL 2000 Enterprise Edition.
> Thanks
> Paul
>
>|||Thanks JP.
Have you got 4GB Ram and if so are you just using /3GB and not PAE or AWE.
I have exactly 4GB ram. If I use PAE the slider in enterprise manager shows
4GB max. With /3GB I only see 2GB.
I don't want to have the overhead of /PAE and it should not be necessary. Is
there any way to see if /3GB is working (from an NT or SQL)?
Paul
"JP de Jong" <JP de Jong@.discussions.microsoft.com> wrote in message
news:1447D55D-C78C-41E8-87EB-FDF4C0E082D8@.microsoft.com...[vbcol=seagreen]
> Paul,
> The maximum value of the slider should show a value of 3-something . (in
> my
> environments it's 3455).
> I would suggest not setting a fixed size, always let SQL use as much as
> possible.
> JP
> "Paul Cahill" wrote:
>|||Paul
Just checked it for you.
We have 4GB RAM in server (Windows 2003Server). In BoOT.INI we have "/3GB
/PAE". (so we do have PAE enabled).
In properties of system (my computer) it says. Physical Address Extensions
enabled. Not sure how to check if /3GB is enabled. You're absolutelt right
that /PAE only is effective when you have more than 4 GB.
/3GB only enables applications to use more virtual memory. I'm not quite
sure if you can find that back in the gui of SQL.
JP
"Paul Cahill" wrote:
> Thanks JP.
> Have you got 4GB Ram and if so are you just using /3GB and not PAE or AWE.
> I have exactly 4GB ram. If I use PAE the slider in enterprise manager show
s
> 4GB max. With /3GB I only see 2GB.
> I don't want to have the overhead of /PAE and it should not be necessary.
Is
> there any way to see if /3GB is working (from an NT or SQL)?
> Paul
>
> "JP de Jong" <JP de Jong@.discussions.microsoft.com> wrote in message
> news:1447D55D-C78C-41E8-87EB-FDF4C0E082D8@.microsoft.com...
>
>|||Thanks JP.
Any idea why you have /PAE? I thought there's got to be an overhead for
address translation.
You don't feel like trying something for me......
Paul
"JP de Jong" <JPdeJong@.discussions.microsoft.com> wrote in message
news:45DC15E7-3C0D-4DD0-ACEE-732E9A8504E0@.microsoft.com...[vbcol=seagreen]
> Paul
> Just checked it for you.
> We have 4GB RAM in server (Windows 2003Server). In BoOT.INI we have "/3GB
> /PAE". (so we do have PAE enabled).
> In properties of system (my computer) it says. Physical Address Extensions
> enabled. Not sure how to check if /3GB is enabled. You're absolutelt right
> that /PAE only is effective when you have more than 4 GB.
> /3GB only enables applications to use more virtual memory. I'm not quite
> sure if you can find that back in the gui of SQL.
> JP
> "Paul Cahill" wrote:
>
Manager display up to 3GB or do you set manually and just assume it's
working?
2000 Advanced server and SQL 2000 Enterprise Edition.
Thanks
PaulPaul,
The maximum value of the slider should show a value of 3-something . (in my
environments it's 3455).
I would suggest not setting a fixed size, always let SQL use as much as
possible.
JP
"Paul Cahill" wrote:
> If you use the /3GB switch should the memory slider in SQL Enterprise
> Manager display up to 3GB or do you set manually and just assume it's
> working?
> 2000 Advanced server and SQL 2000 Enterprise Edition.
> Thanks
> Paul
>
>|||Thanks JP.
Have you got 4GB Ram and if so are you just using /3GB and not PAE or AWE.
I have exactly 4GB ram. If I use PAE the slider in enterprise manager shows
4GB max. With /3GB I only see 2GB.
I don't want to have the overhead of /PAE and it should not be necessary. Is
there any way to see if /3GB is working (from an NT or SQL)?
Paul
"JP de Jong" <JP de Jong@.discussions.microsoft.com> wrote in message
news:1447D55D-C78C-41E8-87EB-FDF4C0E082D8@.microsoft.com...[vbcol=seagreen]
> Paul,
> The maximum value of the slider should show a value of 3-something . (in
> my
> environments it's 3455).
> I would suggest not setting a fixed size, always let SQL use as much as
> possible.
> JP
> "Paul Cahill" wrote:
>|||Paul
Just checked it for you.
We have 4GB RAM in server (Windows 2003Server). In BoOT.INI we have "/3GB
/PAE". (so we do have PAE enabled).
In properties of system (my computer) it says. Physical Address Extensions
enabled. Not sure how to check if /3GB is enabled. You're absolutelt right
that /PAE only is effective when you have more than 4 GB.
/3GB only enables applications to use more virtual memory. I'm not quite
sure if you can find that back in the gui of SQL.
JP
"Paul Cahill" wrote:
> Thanks JP.
> Have you got 4GB Ram and if so are you just using /3GB and not PAE or AWE.
> I have exactly 4GB ram. If I use PAE the slider in enterprise manager show
s
> 4GB max. With /3GB I only see 2GB.
> I don't want to have the overhead of /PAE and it should not be necessary.
Is
> there any way to see if /3GB is working (from an NT or SQL)?
> Paul
>
> "JP de Jong" <JP de Jong@.discussions.microsoft.com> wrote in message
> news:1447D55D-C78C-41E8-87EB-FDF4C0E082D8@.microsoft.com...
>
>|||Thanks JP.
Any idea why you have /PAE? I thought there's got to be an overhead for
address translation.
You don't feel like trying something for me......
Paul
"JP de Jong" <JPdeJong@.discussions.microsoft.com> wrote in message
news:45DC15E7-3C0D-4DD0-ACEE-732E9A8504E0@.microsoft.com...[vbcol=seagreen]
> Paul
> Just checked it for you.
> We have 4GB RAM in server (Windows 2003Server). In BoOT.INI we have "/3GB
> /PAE". (so we do have PAE enabled).
> In properties of system (my computer) it says. Physical Address Extensions
> enabled. Not sure how to check if /3GB is enabled. You're absolutelt right
> that /PAE only is effective when you have more than 4 GB.
> /3GB only enables applications to use more virtual memory. I'm not quite
> sure if you can find that back in the gui of SQL.
> JP
> "Paul Cahill" wrote:
>
4GB Ram /3GB and the memory slider in Ent Manager
If you use the /3GB switch should the memory slider in SQL Enterprise
Manager display up to 3GB or do you set manually and just assume it's
working?
2000 Advanced server and SQL 2000 Enterprise Edition.
Thanks
PaulPaul,
The maximum value of the slider should show a value of 3-something . (in my
environments it's 3455).
I would suggest not setting a fixed size, always let SQL use as much as
possible.
JP
"Paul Cahill" wrote:
> If you use the /3GB switch should the memory slider in SQL Enterprise
> Manager display up to 3GB or do you set manually and just assume it's
> working?
> 2000 Advanced server and SQL 2000 Enterprise Edition.
> Thanks
> Paul
>
>|||Thanks JP.
Have you got 4GB Ram and if so are you just using /3GB and not PAE or AWE.
I have exactly 4GB ram. If I use PAE the slider in enterprise manager shows
4GB max. With /3GB I only see 2GB.
I don't want to have the overhead of /PAE and it should not be necessary. Is
there any way to see if /3GB is working (from an NT or SQL)?
Paul
"JP de Jong" <JP de Jong@.discussions.microsoft.com> wrote in message
news:1447D55D-C78C-41E8-87EB-FDF4C0E082D8@.microsoft.com...
> Paul,
> The maximum value of the slider should show a value of 3-something . (in
> my
> environments it's 3455).
> I would suggest not setting a fixed size, always let SQL use as much as
> possible.
> JP
> "Paul Cahill" wrote:
>> If you use the /3GB switch should the memory slider in SQL Enterprise
>> Manager display up to 3GB or do you set manually and just assume it's
>> working?
>> 2000 Advanced server and SQL 2000 Enterprise Edition.
>> Thanks
>> Paul
>>|||Paul
Just checked it for you.
We have 4GB RAM in server (Windows 2003Server). In BoOT.INI we have "/3GB
/PAE". (so we do have PAE enabled).
In properties of system (my computer) it says. Physical Address Extensions
enabled. Not sure how to check if /3GB is enabled. You're absolutelt right
that /PAE only is effective when you have more than 4 GB.
/3GB only enables applications to use more virtual memory. I'm not quite
sure if you can find that back in the gui of SQL.
JP
"Paul Cahill" wrote:
> Thanks JP.
> Have you got 4GB Ram and if so are you just using /3GB and not PAE or AWE.
> I have exactly 4GB ram. If I use PAE the slider in enterprise manager shows
> 4GB max. With /3GB I only see 2GB.
> I don't want to have the overhead of /PAE and it should not be necessary. Is
> there any way to see if /3GB is working (from an NT or SQL)?
> Paul
>
> "JP de Jong" <JP de Jong@.discussions.microsoft.com> wrote in message
> news:1447D55D-C78C-41E8-87EB-FDF4C0E082D8@.microsoft.com...
> > Paul,
> >
> > The maximum value of the slider should show a value of 3-something . (in
> > my
> > environments it's 3455).
> >
> > I would suggest not setting a fixed size, always let SQL use as much as
> > possible.
> >
> > JP
> >
> > "Paul Cahill" wrote:
> >
> >> If you use the /3GB switch should the memory slider in SQL Enterprise
> >> Manager display up to 3GB or do you set manually and just assume it's
> >> working?
> >> 2000 Advanced server and SQL 2000 Enterprise Edition.
> >>
> >> Thanks
> >> Paul
> >>
> >>
> >>
>
>|||Thanks JP.
Any idea why you have /PAE? I thought there's got to be an overhead for
address translation.
You don't feel like trying something for me......
Paul
"JP de Jong" <JPdeJong@.discussions.microsoft.com> wrote in message
news:45DC15E7-3C0D-4DD0-ACEE-732E9A8504E0@.microsoft.com...
> Paul
> Just checked it for you.
> We have 4GB RAM in server (Windows 2003Server). In BoOT.INI we have "/3GB
> /PAE". (so we do have PAE enabled).
> In properties of system (my computer) it says. Physical Address Extensions
> enabled. Not sure how to check if /3GB is enabled. You're absolutelt right
> that /PAE only is effective when you have more than 4 GB.
> /3GB only enables applications to use more virtual memory. I'm not quite
> sure if you can find that back in the gui of SQL.
> JP
> "Paul Cahill" wrote:
>> Thanks JP.
>> Have you got 4GB Ram and if so are you just using /3GB and not PAE or
>> AWE.
>> I have exactly 4GB ram. If I use PAE the slider in enterprise manager
>> shows
>> 4GB max. With /3GB I only see 2GB.
>> I don't want to have the overhead of /PAE and it should not be necessary.
>> Is
>> there any way to see if /3GB is working (from an NT or SQL)?
>> Paul
>>
>> "JP de Jong" <JP de Jong@.discussions.microsoft.com> wrote in message
>> news:1447D55D-C78C-41E8-87EB-FDF4C0E082D8@.microsoft.com...
>> > Paul,
>> >
>> > The maximum value of the slider should show a value of 3-something .
>> > (in
>> > my
>> > environments it's 3455).
>> >
>> > I would suggest not setting a fixed size, always let SQL use as much as
>> > possible.
>> >
>> > JP
>> >
>> > "Paul Cahill" wrote:
>> >
>> >> If you use the /3GB switch should the memory slider in SQL Enterprise
>> >> Manager display up to 3GB or do you set manually and just assume it's
>> >> working?
>> >> 2000 Advanced server and SQL 2000 Enterprise Edition.
>> >>
>> >> Thanks
>> >> Paul
>> >>
>> >>
>> >>
>>
Manager display up to 3GB or do you set manually and just assume it's
working?
2000 Advanced server and SQL 2000 Enterprise Edition.
Thanks
PaulPaul,
The maximum value of the slider should show a value of 3-something . (in my
environments it's 3455).
I would suggest not setting a fixed size, always let SQL use as much as
possible.
JP
"Paul Cahill" wrote:
> If you use the /3GB switch should the memory slider in SQL Enterprise
> Manager display up to 3GB or do you set manually and just assume it's
> working?
> 2000 Advanced server and SQL 2000 Enterprise Edition.
> Thanks
> Paul
>
>|||Thanks JP.
Have you got 4GB Ram and if so are you just using /3GB and not PAE or AWE.
I have exactly 4GB ram. If I use PAE the slider in enterprise manager shows
4GB max. With /3GB I only see 2GB.
I don't want to have the overhead of /PAE and it should not be necessary. Is
there any way to see if /3GB is working (from an NT or SQL)?
Paul
"JP de Jong" <JP de Jong@.discussions.microsoft.com> wrote in message
news:1447D55D-C78C-41E8-87EB-FDF4C0E082D8@.microsoft.com...
> Paul,
> The maximum value of the slider should show a value of 3-something . (in
> my
> environments it's 3455).
> I would suggest not setting a fixed size, always let SQL use as much as
> possible.
> JP
> "Paul Cahill" wrote:
>> If you use the /3GB switch should the memory slider in SQL Enterprise
>> Manager display up to 3GB or do you set manually and just assume it's
>> working?
>> 2000 Advanced server and SQL 2000 Enterprise Edition.
>> Thanks
>> Paul
>>|||Paul
Just checked it for you.
We have 4GB RAM in server (Windows 2003Server). In BoOT.INI we have "/3GB
/PAE". (so we do have PAE enabled).
In properties of system (my computer) it says. Physical Address Extensions
enabled. Not sure how to check if /3GB is enabled. You're absolutelt right
that /PAE only is effective when you have more than 4 GB.
/3GB only enables applications to use more virtual memory. I'm not quite
sure if you can find that back in the gui of SQL.
JP
"Paul Cahill" wrote:
> Thanks JP.
> Have you got 4GB Ram and if so are you just using /3GB and not PAE or AWE.
> I have exactly 4GB ram. If I use PAE the slider in enterprise manager shows
> 4GB max. With /3GB I only see 2GB.
> I don't want to have the overhead of /PAE and it should not be necessary. Is
> there any way to see if /3GB is working (from an NT or SQL)?
> Paul
>
> "JP de Jong" <JP de Jong@.discussions.microsoft.com> wrote in message
> news:1447D55D-C78C-41E8-87EB-FDF4C0E082D8@.microsoft.com...
> > Paul,
> >
> > The maximum value of the slider should show a value of 3-something . (in
> > my
> > environments it's 3455).
> >
> > I would suggest not setting a fixed size, always let SQL use as much as
> > possible.
> >
> > JP
> >
> > "Paul Cahill" wrote:
> >
> >> If you use the /3GB switch should the memory slider in SQL Enterprise
> >> Manager display up to 3GB or do you set manually and just assume it's
> >> working?
> >> 2000 Advanced server and SQL 2000 Enterprise Edition.
> >>
> >> Thanks
> >> Paul
> >>
> >>
> >>
>
>|||Thanks JP.
Any idea why you have /PAE? I thought there's got to be an overhead for
address translation.
You don't feel like trying something for me......
Paul
"JP de Jong" <JPdeJong@.discussions.microsoft.com> wrote in message
news:45DC15E7-3C0D-4DD0-ACEE-732E9A8504E0@.microsoft.com...
> Paul
> Just checked it for you.
> We have 4GB RAM in server (Windows 2003Server). In BoOT.INI we have "/3GB
> /PAE". (so we do have PAE enabled).
> In properties of system (my computer) it says. Physical Address Extensions
> enabled. Not sure how to check if /3GB is enabled. You're absolutelt right
> that /PAE only is effective when you have more than 4 GB.
> /3GB only enables applications to use more virtual memory. I'm not quite
> sure if you can find that back in the gui of SQL.
> JP
> "Paul Cahill" wrote:
>> Thanks JP.
>> Have you got 4GB Ram and if so are you just using /3GB and not PAE or
>> AWE.
>> I have exactly 4GB ram. If I use PAE the slider in enterprise manager
>> shows
>> 4GB max. With /3GB I only see 2GB.
>> I don't want to have the overhead of /PAE and it should not be necessary.
>> Is
>> there any way to see if /3GB is working (from an NT or SQL)?
>> Paul
>>
>> "JP de Jong" <JP de Jong@.discussions.microsoft.com> wrote in message
>> news:1447D55D-C78C-41E8-87EB-FDF4C0E082D8@.microsoft.com...
>> > Paul,
>> >
>> > The maximum value of the slider should show a value of 3-something .
>> > (in
>> > my
>> > environments it's 3455).
>> >
>> > I would suggest not setting a fixed size, always let SQL use as much as
>> > possible.
>> >
>> > JP
>> >
>> > "Paul Cahill" wrote:
>> >
>> >> If you use the /3GB switch should the memory slider in SQL Enterprise
>> >> Manager display up to 3GB or do you set manually and just assume it's
>> >> working?
>> >> 2000 Advanced server and SQL 2000 Enterprise Edition.
>> >>
>> >> Thanks
>> >> Paul
>> >>
>> >>
>> >>
>>
Thursday, February 9, 2012
3GB and 4GB RAM on SQL 2000 Ent, Win 2003 Ent
We have two SQL servers that we need to optimize the RAM for SQL server.
Both servers are running SQL 2000 Enterprise with Windows 2003 Enterprise.
What is the optimum boot.ini settings and SQL settings for these servers.
From what I have read so far, it seems I need to do the following:
On the 3 GB server, simply add the /3GB option in the boot.ini.
On the 4 GB server, simply add the /3GB option in the boot.ini as well. It
seems I only need to turn awe on the SQL server if it has more than 4 GB of
RAM.
Can anyone clarify this for me? Are there any known issues using these
settings?
Thank You,
KevinYou are correct. AWE is only needed if you have more than 4GB of physical
memory in the box. Do not use /3GB with more than (12,16) GB of RAM. I
have heard different recommendations so pick either 12 or 16 GB as your
choice.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Kevin Hammond" <kghammond@.nrscorp.com> wrote in message
news:ck0pvg$77j$1@.grandcanyon.binc.net...
> We have two SQL servers that we need to optimize the RAM for SQL server.
> Both servers are running SQL 2000 Enterprise with Windows 2003 Enterprise.
> What is the optimum boot.ini settings and SQL settings for these servers.
> From what I have read so far, it seems I need to do the following:
> On the 3 GB server, simply add the /3GB option in the boot.ini.
> On the 4 GB server, simply add the /3GB option in the boot.ini as well.
It
> seems I only need to turn awe on the SQL server if it has more than 4 GB
of
> RAM.
> Can anyone clarify this for me? Are there any known issues using these
> settings?
> Thank You,
> Kevin
>|||i don't think this is right. you need the AWE option of
sql server in any case. the question is only if you need
also the /PAE switch.
for clarifying this check out the MS KB-article 274750
"How to configure memory for more than 2 GB in SQL Server"
http://support.microsoft.com/default.aspx?scid=kb;en-
us;274750
>--Original Message--
>You are correct. AWE is only needed if you have more
than 4GB of physical
>memory in the box. Do not use /3GB with more than
(12,16) GB of RAM. I
>have heard different recommendations so pick either 12 or
16 GB as your
>choice.
>--
>Geoff N. Hiten
>Microsoft SQL Server MVP
>Senior Database Administrator
>Careerbuilder.com
>I support the Professional Association for SQL Server
>www.sqlpass.org
>"Kevin Hammond" <kghammond@.nrscorp.com> wrote in message
>news:ck0pvg$77j$1@.grandcanyon.binc.net...
>> We have two SQL servers that we need to optimize the
RAM for SQL server.
>> Both servers are running SQL 2000 Enterprise with
Windows 2003 Enterprise.
>> What is the optimum boot.ini settings and SQL settings
for these servers.
>> From what I have read so far, it seems I need to do the
following:
>> On the 3 GB server, simply add the /3GB option in the
boot.ini.
>> On the 4 GB server, simply add the /3GB option in the
boot.ini as well.
>It
>> seems I only need to turn awe on the SQL server if it
has more than 4 GB
>of
>> RAM.
>> Can anyone clarify this for me? Are there any known
issues using these
>> settings?
>> Thank You,
>> Kevin
>>
>
>.
>|||If you only have 4GB it is probably better to let SQL Server have 3GB and let the OS have the rest
of the memory. Using PAE is not for free and it is also a bit if extra admin burden.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Juliane" <anonymous@.discussions.microsoft.com> wrote in message
news:0d2001c4abc3$08586640$a401280a@.phx.gbl...
>i don't think this is right. you need the AWE option of
> sql server in any case. the question is only if you need
> also the /PAE switch.
> for clarifying this check out the MS KB-article 274750
> "How to configure memory for more than 2 GB in SQL Server"
> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;274750
>
>
>>--Original Message--
>>You are correct. AWE is only needed if you have more
> than 4GB of physical
>>memory in the box. Do not use /3GB with more than
> (12,16) GB of RAM. I
>>have heard different recommendations so pick either 12 or
> 16 GB as your
>>choice.
>>--
>>Geoff N. Hiten
>>Microsoft SQL Server MVP
>>Senior Database Administrator
>>Careerbuilder.com
>>I support the Professional Association for SQL Server
>>www.sqlpass.org
>>"Kevin Hammond" <kghammond@.nrscorp.com> wrote in message
>>news:ck0pvg$77j$1@.grandcanyon.binc.net...
>> We have two SQL servers that we need to optimize the
> RAM for SQL server.
>> Both servers are running SQL 2000 Enterprise with
> Windows 2003 Enterprise.
>> What is the optimum boot.ini settings and SQL settings
> for these servers.
>> From what I have read so far, it seems I need to do the
> following:
>> On the 3 GB server, simply add the /3GB option in the
> boot.ini.
>> On the 4 GB server, simply add the /3GB option in the
> boot.ini as well.
>>It
>> seems I only need to turn awe on the SQL server if it
> has more than 4 GB
>>of
>> RAM.
>> Can anyone clarify this for me? Are there any known
> issues using these
>> settings?
>> Thank You,
>> Kevin
>>
>>
>>.
Both servers are running SQL 2000 Enterprise with Windows 2003 Enterprise.
What is the optimum boot.ini settings and SQL settings for these servers.
From what I have read so far, it seems I need to do the following:
On the 3 GB server, simply add the /3GB option in the boot.ini.
On the 4 GB server, simply add the /3GB option in the boot.ini as well. It
seems I only need to turn awe on the SQL server if it has more than 4 GB of
RAM.
Can anyone clarify this for me? Are there any known issues using these
settings?
Thank You,
KevinYou are correct. AWE is only needed if you have more than 4GB of physical
memory in the box. Do not use /3GB with more than (12,16) GB of RAM. I
have heard different recommendations so pick either 12 or 16 GB as your
choice.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Kevin Hammond" <kghammond@.nrscorp.com> wrote in message
news:ck0pvg$77j$1@.grandcanyon.binc.net...
> We have two SQL servers that we need to optimize the RAM for SQL server.
> Both servers are running SQL 2000 Enterprise with Windows 2003 Enterprise.
> What is the optimum boot.ini settings and SQL settings for these servers.
> From what I have read so far, it seems I need to do the following:
> On the 3 GB server, simply add the /3GB option in the boot.ini.
> On the 4 GB server, simply add the /3GB option in the boot.ini as well.
It
> seems I only need to turn awe on the SQL server if it has more than 4 GB
of
> RAM.
> Can anyone clarify this for me? Are there any known issues using these
> settings?
> Thank You,
> Kevin
>|||i don't think this is right. you need the AWE option of
sql server in any case. the question is only if you need
also the /PAE switch.
for clarifying this check out the MS KB-article 274750
"How to configure memory for more than 2 GB in SQL Server"
http://support.microsoft.com/default.aspx?scid=kb;en-
us;274750
>--Original Message--
>You are correct. AWE is only needed if you have more
than 4GB of physical
>memory in the box. Do not use /3GB with more than
(12,16) GB of RAM. I
>have heard different recommendations so pick either 12 or
16 GB as your
>choice.
>--
>Geoff N. Hiten
>Microsoft SQL Server MVP
>Senior Database Administrator
>Careerbuilder.com
>I support the Professional Association for SQL Server
>www.sqlpass.org
>"Kevin Hammond" <kghammond@.nrscorp.com> wrote in message
>news:ck0pvg$77j$1@.grandcanyon.binc.net...
>> We have two SQL servers that we need to optimize the
RAM for SQL server.
>> Both servers are running SQL 2000 Enterprise with
Windows 2003 Enterprise.
>> What is the optimum boot.ini settings and SQL settings
for these servers.
>> From what I have read so far, it seems I need to do the
following:
>> On the 3 GB server, simply add the /3GB option in the
boot.ini.
>> On the 4 GB server, simply add the /3GB option in the
boot.ini as well.
>It
>> seems I only need to turn awe on the SQL server if it
has more than 4 GB
>of
>> RAM.
>> Can anyone clarify this for me? Are there any known
issues using these
>> settings?
>> Thank You,
>> Kevin
>>
>
>.
>|||If you only have 4GB it is probably better to let SQL Server have 3GB and let the OS have the rest
of the memory. Using PAE is not for free and it is also a bit if extra admin burden.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Juliane" <anonymous@.discussions.microsoft.com> wrote in message
news:0d2001c4abc3$08586640$a401280a@.phx.gbl...
>i don't think this is right. you need the AWE option of
> sql server in any case. the question is only if you need
> also the /PAE switch.
> for clarifying this check out the MS KB-article 274750
> "How to configure memory for more than 2 GB in SQL Server"
> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;274750
>
>
>>--Original Message--
>>You are correct. AWE is only needed if you have more
> than 4GB of physical
>>memory in the box. Do not use /3GB with more than
> (12,16) GB of RAM. I
>>have heard different recommendations so pick either 12 or
> 16 GB as your
>>choice.
>>--
>>Geoff N. Hiten
>>Microsoft SQL Server MVP
>>Senior Database Administrator
>>Careerbuilder.com
>>I support the Professional Association for SQL Server
>>www.sqlpass.org
>>"Kevin Hammond" <kghammond@.nrscorp.com> wrote in message
>>news:ck0pvg$77j$1@.grandcanyon.binc.net...
>> We have two SQL servers that we need to optimize the
> RAM for SQL server.
>> Both servers are running SQL 2000 Enterprise with
> Windows 2003 Enterprise.
>> What is the optimum boot.ini settings and SQL settings
> for these servers.
>> From what I have read so far, it seems I need to do the
> following:
>> On the 3 GB server, simply add the /3GB option in the
> boot.ini.
>> On the 4 GB server, simply add the /3GB option in the
> boot.ini as well.
>>It
>> seems I only need to turn awe on the SQL server if it
> has more than 4 GB
>>of
>> RAM.
>> Can anyone clarify this for me? Are there any known
> issues using these
>> settings?
>> Thank You,
>> Kevin
>>
>>
>>.
3GB and 4GB RAM on SQL 2000 Ent, Win 2003 Ent
We have two SQL servers that we need to optimize the RAM for SQL server.
Both servers are running SQL 2000 Enterprise with Windows 2003 Enterprise.
What is the optimum boot.ini settings and SQL settings for these servers.
From what I have read so far, it seems I need to do the following:
On the 3 GB server, simply add the /3GB option in the boot.ini.
On the 4 GB server, simply add the /3GB option in the boot.ini as well. It
seems I only need to turn awe on the SQL server if it has more than 4 GB of
RAM.
Can anyone clarify this for me? Are there any known issues using these
settings?
Thank You,
Kevin
You are correct. AWE is only needed if you have more than 4GB of physical
memory in the box. Do not use /3GB with more than (12,16) GB of RAM. I
have heard different recommendations so pick either 12 or 16 GB as your
choice.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Kevin Hammond" <kghammond@.nrscorp.com> wrote in message
news:ck0pvg$77j$1@.grandcanyon.binc.net...
> We have two SQL servers that we need to optimize the RAM for SQL server.
> Both servers are running SQL 2000 Enterprise with Windows 2003 Enterprise.
> What is the optimum boot.ini settings and SQL settings for these servers.
> From what I have read so far, it seems I need to do the following:
> On the 3 GB server, simply add the /3GB option in the boot.ini.
> On the 4 GB server, simply add the /3GB option in the boot.ini as well.
It
> seems I only need to turn awe on the SQL server if it has more than 4 GB
of
> RAM.
> Can anyone clarify this for me? Are there any known issues using these
> settings?
> Thank You,
> Kevin
>
|||i don't think this is right. you need the AWE option of
sql server in any case. the question is only if you need
also the /PAE switch.
for clarifying this check out the MS KB-article 274750
"How to configure memory for more than 2 GB in SQL Server"
http://support.microsoft.com/default.aspx?scid=kb;en-
us;274750
>--Original Message--
>You are correct. AWE is only needed if you have more
than 4GB of physical
>memory in the box. Do not use /3GB with more than
(12,16) GB of RAM. I
>have heard different recommendations so pick either 12 or
16 GB as your[vbcol=seagreen]
>choice.
>--
>Geoff N. Hiten
>Microsoft SQL Server MVP
>Senior Database Administrator
>Careerbuilder.com
>I support the Professional Association for SQL Server
>www.sqlpass.org
>"Kevin Hammond" <kghammond@.nrscorp.com> wrote in message
>news:ck0pvg$77j$1@.grandcanyon.binc.net...
RAM for SQL server.[vbcol=seagreen]
Windows 2003 Enterprise.[vbcol=seagreen]
for these servers.[vbcol=seagreen]
following:[vbcol=seagreen]
boot.ini.[vbcol=seagreen]
boot.ini as well.[vbcol=seagreen]
>It
has more than 4 GB[vbcol=seagreen]
>of
issues using these
>
>.
>
|||If you only have 4GB it is probably better to let SQL Server have 3GB and let the OS have the rest
of the memory. Using PAE is not for free and it is also a bit if extra admin burden.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Juliane" <anonymous@.discussions.microsoft.com> wrote in message
news:0d2001c4abc3$08586640$a401280a@.phx.gbl...[vbcol=seagreen]
>i don't think this is right. you need the AWE option of
> sql server in any case. the question is only if you need
> also the /PAE switch.
> for clarifying this check out the MS KB-article 274750
> "How to configure memory for more than 2 GB in SQL Server"
> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;274750
>
>
> than 4GB of physical
> (12,16) GB of RAM. I
> 16 GB as your
> RAM for SQL server.
> Windows 2003 Enterprise.
> for these servers.
> following:
> boot.ini.
> boot.ini as well.
> has more than 4 GB
> issues using these
Both servers are running SQL 2000 Enterprise with Windows 2003 Enterprise.
What is the optimum boot.ini settings and SQL settings for these servers.
From what I have read so far, it seems I need to do the following:
On the 3 GB server, simply add the /3GB option in the boot.ini.
On the 4 GB server, simply add the /3GB option in the boot.ini as well. It
seems I only need to turn awe on the SQL server if it has more than 4 GB of
RAM.
Can anyone clarify this for me? Are there any known issues using these
settings?
Thank You,
Kevin
You are correct. AWE is only needed if you have more than 4GB of physical
memory in the box. Do not use /3GB with more than (12,16) GB of RAM. I
have heard different recommendations so pick either 12 or 16 GB as your
choice.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Kevin Hammond" <kghammond@.nrscorp.com> wrote in message
news:ck0pvg$77j$1@.grandcanyon.binc.net...
> We have two SQL servers that we need to optimize the RAM for SQL server.
> Both servers are running SQL 2000 Enterprise with Windows 2003 Enterprise.
> What is the optimum boot.ini settings and SQL settings for these servers.
> From what I have read so far, it seems I need to do the following:
> On the 3 GB server, simply add the /3GB option in the boot.ini.
> On the 4 GB server, simply add the /3GB option in the boot.ini as well.
It
> seems I only need to turn awe on the SQL server if it has more than 4 GB
of
> RAM.
> Can anyone clarify this for me? Are there any known issues using these
> settings?
> Thank You,
> Kevin
>
|||i don't think this is right. you need the AWE option of
sql server in any case. the question is only if you need
also the /PAE switch.
for clarifying this check out the MS KB-article 274750
"How to configure memory for more than 2 GB in SQL Server"
http://support.microsoft.com/default.aspx?scid=kb;en-
us;274750
>--Original Message--
>You are correct. AWE is only needed if you have more
than 4GB of physical
>memory in the box. Do not use /3GB with more than
(12,16) GB of RAM. I
>have heard different recommendations so pick either 12 or
16 GB as your[vbcol=seagreen]
>choice.
>--
>Geoff N. Hiten
>Microsoft SQL Server MVP
>Senior Database Administrator
>Careerbuilder.com
>I support the Professional Association for SQL Server
>www.sqlpass.org
>"Kevin Hammond" <kghammond@.nrscorp.com> wrote in message
>news:ck0pvg$77j$1@.grandcanyon.binc.net...
RAM for SQL server.[vbcol=seagreen]
Windows 2003 Enterprise.[vbcol=seagreen]
for these servers.[vbcol=seagreen]
following:[vbcol=seagreen]
boot.ini.[vbcol=seagreen]
boot.ini as well.[vbcol=seagreen]
>It
has more than 4 GB[vbcol=seagreen]
>of
issues using these
>
>.
>
|||If you only have 4GB it is probably better to let SQL Server have 3GB and let the OS have the rest
of the memory. Using PAE is not for free and it is also a bit if extra admin burden.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Juliane" <anonymous@.discussions.microsoft.com> wrote in message
news:0d2001c4abc3$08586640$a401280a@.phx.gbl...[vbcol=seagreen]
>i don't think this is right. you need the AWE option of
> sql server in any case. the question is only if you need
> also the /PAE switch.
> for clarifying this check out the MS KB-article 274750
> "How to configure memory for more than 2 GB in SQL Server"
> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;274750
>
>
> than 4GB of physical
> (12,16) GB of RAM. I
> 16 GB as your
> RAM for SQL server.
> Windows 2003 Enterprise.
> for these servers.
> following:
> boot.ini.
> boot.ini as well.
> has more than 4 GB
> issues using these
Subscribe to:
Posts (Atom)