Boot.ini file: bootini

Showing posts with label bootini. Show all posts

Friday, February 10, 2012

BOOT.INI File for 4GB RAM and SQL 2005

I have 3 questions regarding memory configuration on a Windows Server 2003
SP2 Enterprise Edition with SQL2005 SP2.
1. Can someone advise on the correct boot.ini file configuration to utilize
4GB of local memory? I'm not sure if I need the 3GB switch?
multi(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003,
Enterprise"/3GB/fastdetect/PAE/NoExectute=OptOut
2. Once Boot.ini configured, is the only setting in SQL 2005 to modify is
the sp_configure awe enabled config_value=1 and run_value=1 ?
3. Assuming nothing else is to be done to have SQL 2005 utilize more than
the 2GB memory space, how do you verify or validate SQL 2005 is using more
memory?
Thanks in advancezorro
Is it 64 bit or 32 bit?
> 1. Can someone advise on the correct boot.ini file configuration to
> utilize
> 4GB of local memory? I'm not sure if I need the 3GB switch?
You do need 3GB switch
> 2. Once Boot.ini configured, is the only setting in SQL 2005 to modify is
> the sp_configure awe enabled config_value=1 and run_value=1 ?
AWE is for utilyze more than 4GB
Yes, unless you use 64 bit , then you do not need AWE , make sure that an
account SQL Serverc runs under is added to LockPages in Memory Local Group
Policy
> 3. Assuming nothing else is to be done to have SQL 2005 utilize more than
> the 2GB memory space, how do you verify or validate SQL 2005 is using more
> memory?
Task Manager
"zorro" <zorro@.discussions.microsoft.com> wrote in message
news:C2009B55-7B5D-4F65-8986-3AF00547FA1E@.microsoft.com...
>I have 3 questions regarding memory configuration on a Windows Server 2003
> SP2 Enterprise Edition with SQL2005 SP2.
> 1. Can someone advise on the correct boot.ini file configuration to
> utilize
> 4GB of local memory? I'm not sure if I need the 3GB switch?
> multi(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003,
> Enterprise"/3GB/fastdetect/PAE/NoExectute=OptOut
> 2. Once Boot.ini configured, is the only setting in SQL 2005 to modify is
> the sp_configure awe enabled config_value=1 and run_value=1 ?
> 3. Assuming nothing else is to be done to have SQL 2005 utilize more than
> the 2GB memory space, how do you verify or validate SQL 2005 is using more
> memory?
> Thanks in advance
>|||>> 3. Assuming nothing else is to be done to have SQL 2005 utilize more than
>> the 2GB memory space, how do you verify or validate SQL 2005 is using
>> more
>> memory?
> Task Manager
Actually, I would use performance monitor. Task manager tends to
under-report what SQL Server is actually using.|||Aaron
I agreee. I assumed the OP wants to utilize 4GB ONLY , so after adding
3GB switch you can actually observe in TM.
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:%23qL67StfIHA.5088@.TK2MSFTNGP02.phx.gbl...
>> 3. Assuming nothing else is to be done to have SQL 2005 utilize more
>> than
>> the 2GB memory space, how do you verify or validate SQL 2005 is using
>> more
>> memory?
>> Task Manager
> Actually, I would use performance monitor. Task manager tends to
> under-report what SQL Server is actually using.|||Thanks Uri,
1. 32 bit Windows Server 2003 version.
2. To verify 3GB switch is needed for my 5GB physically installed RAM?
3. Also good catch on the LockPages in Memory setting within the gpedit.msc
Thanks,
zorro
"Uri Dimant" wrote:
> zorro
> Is it 64 bit or 32 bit?
> > 1. Can someone advise on the correct boot.ini file configuration to
> > utilize
> > 4GB of local memory? I'm not sure if I need the 3GB switch?
> You do need 3GB switch
> > 2. Once Boot.ini configured, is the only setting in SQL 2005 to modify is
> > the sp_configure awe enabled config_value=1 and run_value=1 ?
> AWE is for utilyze more than 4GB
> Yes, unless you use 64 bit , then you do not need AWE , make sure that an
> account SQL Serverc runs under is added to LockPages in Memory Local Group
> Policy
> > 3. Assuming nothing else is to be done to have SQL 2005 utilize more than
> > the 2GB memory space, how do you verify or validate SQL 2005 is using more
> > memory?
> Task Manager
>
>
> "zorro" <zorro@.discussions.microsoft.com> wrote in message
> news:C2009B55-7B5D-4F65-8986-3AF00547FA1E@.microsoft.com...
> >I have 3 questions regarding memory configuration on a Windows Server 2003
> > SP2 Enterprise Edition with SQL2005 SP2.
> >
> > 1. Can someone advise on the correct boot.ini file configuration to
> > utilize
> > 4GB of local memory? I'm not sure if I need the 3GB switch?
> >
> > multi(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003,
> > Enterprise"/3GB/fastdetect/PAE/NoExectute=OptOut
> >
> > 2. Once Boot.ini configured, is the only setting in SQL 2005 to modify is
> > the sp_configure awe enabled config_value=1 and run_value=1 ?
> >
> > 3. Assuming nothing else is to be done to have SQL 2005 utilize more than
> > the 2GB memory space, how do you verify or validate SQL 2005 is using more
> > memory?
> >
> > Thanks in advance
> >
> >
>
>|||See comments inline.
Linchi
"Uri Dimant" wrote:
> zorro
> Is it 64 bit or 32 bit?
> > 1. Can someone advise on the correct boot.ini file configuration to
> > utilize
> > 4GB of local memory? I'm not sure if I need the 3GB switch?
> You do need 3GB switch
>
Why?
> > 2. Once Boot.ini configured, is the only setting in SQL 2005 to modify is
> > the sp_configure awe enabled config_value=1 and run_value=1 ?
> AWE is for utilyze more than 4GB
I keep hearing that AWE is for utilizing more than 4GB. Not sure where that
comes from. Technically, it's not.
> Yes, unless you use 64 bit , then you do not need AWE , make sure that an
> account SQL Serverc runs under is added to LockPages in Memory Local Group
> Policy
> > 3. Assuming nothing else is to be done to have SQL 2005 utilize more than
> > the 2GB memory space, how do you verify or validate SQL 2005 is using more
> > memory?
> Task Manager
>
>
> "zorro" <zorro@.discussions.microsoft.com> wrote in message
> news:C2009B55-7B5D-4F65-8986-3AF00547FA1E@.microsoft.com...
> >I have 3 questions regarding memory configuration on a Windows Server 2003
> > SP2 Enterprise Edition with SQL2005 SP2.
> >
> > 1. Can someone advise on the correct boot.ini file configuration to
> > utilize
> > 4GB of local memory? I'm not sure if I need the 3GB switch?
> >
> > multi(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003,
> > Enterprise"/3GB/fastdetect/PAE/NoExectute=OptOut
> >
> > 2. Once Boot.ini configured, is the only setting in SQL 2005 to modify is
> > the sp_configure awe enabled config_value=1 and run_value=1 ?
> >
> > 3. Assuming nothing else is to be done to have SQL 2005 utilize more than
> > the 2GB memory space, how do you verify or validate SQL 2005 is using more
> > memory?
> >
> > Thanks in advance
> >
> >
>
>|||Hi Linchi
You are right, that technically, it's not. If I have 4GB RAM and want tio
utilize 3GB for SQL Server, so I simple add switch in BOOT.INI and why
bother enabling AWE? What do you think?
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:61A4195E-F98E-4AE2-A24F-0BC6AC668D08@.microsoft.com...
> See comments inline.
> Linchi
> "Uri Dimant" wrote:
>> zorro
>> Is it 64 bit or 32 bit?
>> > 1. Can someone advise on the correct boot.ini file configuration to
>> > utilize
>> > 4GB of local memory? I'm not sure if I need the 3GB switch?
>> You do need 3GB switch
> Why?
>> > 2. Once Boot.ini configured, is the only setting in SQL 2005 to modify
>> > is
>> > the sp_configure awe enabled config_value=1 and run_value=1 ?
>> AWE is for utilyze more than 4GB
> I keep hearing that AWE is for utilizing more than 4GB. Not sure where
> that
> comes from. Technically, it's not.
>> Yes, unless you use 64 bit , then you do not need AWE , make sure that
>> an
>> account SQL Serverc runs under is added to LockPages in Memory Local
>> Group
>> Policy
>> > 3. Assuming nothing else is to be done to have SQL 2005 utilize more
>> > than
>> > the 2GB memory space, how do you verify or validate SQL 2005 is using
>> > more
>> > memory?
>> Task Manager
>>
>>
>> "zorro" <zorro@.discussions.microsoft.com> wrote in message
>> news:C2009B55-7B5D-4F65-8986-3AF00547FA1E@.microsoft.com...
>> >I have 3 questions regarding memory configuration on a Windows Server
>> >2003
>> > SP2 Enterprise Edition with SQL2005 SP2.
>> >
>> > 1. Can someone advise on the correct boot.ini file configuration to
>> > utilize
>> > 4GB of local memory? I'm not sure if I need the 3GB switch?
>> >
>> > multi(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003,
>> > Enterprise"/3GB/fastdetect/PAE/NoExectute=OptOut
>> >
>> > 2. Once Boot.ini configured, is the only setting in SQL 2005 to modify
>> > is
>> > the sp_configure awe enabled config_value=1 and run_value=1 ?
>> >
>> > 3. Assuming nothing else is to be done to have SQL 2005 utilize more
>> > than
>> > the 2GB memory space, how do you verify or validate SQL 2005 is using
>> > more
>> > memory?
>> >
>> > Thanks in advance
>> >
>> >
>>

BOOT.INI File for 4GB RAM and SQL 2005

Boot.ini file

I ahve SQL Server 2000 running on Windows 2000 Advenced
Server with 8GB physical memory.
When I add both /3GB and /PAE sametime in boot.ini file,
are there any disadvantage effects for server
performance? For SQL or operating system?
Thanks for suggestions.
-TomAs far as I know you can only use that switch on Advance or Datacenter.
See Q274750
Mario

Boot.ini file

boot.ini /3GB problem

Hello,
I have win 2k3 standard edition, 4 GB of memory, SQL 2000 enterprise
edition. I have tryed to get more than 2 GB for sql. I have tryed /3GB swich
with awe enabled on sql 2000 without any good result. I could said even
situation is wors because now sql allocate maximum 1,327 GB.
Does anyone hnow what can be wrong '
I have read many of support pages from MS for allocate more than 2G and
nothing is working :(
regards
Pawel MylkaHi
Task manager is not the correct tool to evaluate if memory over 2 GB is
being used as it is not capable of it.
Use Windows Performance Monitor (%SystemRoot%\system32\perfmon.msc /s) to
see how much "Target Server Memory" is. It should be close to 2700 when SQL
Server is configured correctly.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Pawel Mylka" <pawel.mylka@.itcontrol.pl> wrote in message
news:eEnOZij4FHA.252@.TK2MSFTNGP15.phx.gbl...
> Hello,
> I have win 2k3 standard edition, 4 GB of memory, SQL 2000 enterprise
> edition. I have tryed to get more than 2 GB for sql. I have tryed /3GB
> swich
> with awe enabled on sql 2000 without any good result. I could said even
> situation is wors because now sql allocate maximum 1,327 GB.
> Does anyone hnow what can be wrong '
> I have read many of support pages from MS for allocate more than 2G and
> nothing is working :(
> regards
> Pawel Mylka
>|||Hi,
As Mike pointed out use Performance monitor to view the memory usage. As
well as make the memory static (set min and max meory)
once you enable AWE to SQL Server.
Thanks
Hari
SQL Server MVP
"Pawel Mylka" <pawel.mylka@.itcontrol.pl> wrote in message
news:eEnOZij4FHA.252@.TK2MSFTNGP15.phx.gbl...
> Hello,
> I have win 2k3 standard edition, 4 GB of memory, SQL 2000 enterprise
> edition. I have tryed to get more than 2 GB for sql. I have tryed /3GB
> swich
> with awe enabled on sql 2000 without any good result. I could said even
> situation is wors because now sql allocate maximum 1,327 GB.
> Does anyone hnow what can be wrong '
> I have read many of support pages from MS for allocate more than 2G and
> nothing is working :(
> regards
> Pawel Mylka
>|||Don't enable AWE unless you intend to go beyond 3GB.
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:OoI%23Nzt4FHA.3876@.TK2MSFTNGP09.phx.gbl...
> Hi,
> As Mike pointed out use Performance monitor to view the memory usage. As
> well as make the memory static (set min and max meory)
> once you enable AWE to SQL Server.
> Thanks
> Hari
> SQL Server MVP
> "Pawel Mylka" <pawel.mylka@.itcontrol.pl> wrote in message
> news:eEnOZij4FHA.252@.TK2MSFTNGP15.phx.gbl...
>> Hello,
>> I have win 2k3 standard edition, 4 GB of memory, SQL 2000 enterprise
>> edition. I have tryed to get more than 2 GB for sql. I have tryed /3GB
>> swich
>> with awe enabled on sql 2000 without any good result. I could said even
>> situation is wors because now sql allocate maximum 1,327 GB.
>> Does anyone hnow what can be wrong '
>> I have read many of support pages from MS for allocate more than 2G and
>> nothing is working :(
>> regards
>> Pawel Mylka
>>
>

boot.ini /3GB problem

regards
Pawel Mylka
Hi
Task manager is not the correct tool to evaluate if memory over 2 GB is
being used as it is not capable of it.
Use Windows Performance Monitor (%SystemRoot%\system32\perfmon.msc /s) to
see how much "Target Server Memory" is. It should be close to 2700 when SQL
Server is configured correctly.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Pawel Mylka" <pawel.mylka@.itcontrol.pl> wrote in message
news:eEnOZij4FHA.252@.TK2MSFTNGP15.phx.gbl...
> Hello,
> I have win 2k3 standard edition, 4 GB of memory, SQL 2000 enterprise
> edition. I have tryed to get more than 2 GB for sql. I have tryed /3GB
> swich
> with awe enabled on sql 2000 without any good result. I could said even
> situation is wors because now sql allocate maximum 1,327 GB.
> Does anyone hnow what can be wrong ?
> I have read many of support pages from MS for allocate more than 2G and
> nothing is working

> regards
> Pawel Mylka
>
|||Hi,
As Mike pointed out use Performance monitor to view the memory usage. As
well as make the memory static (set min and max meory)
once you enable AWE to SQL Server.
Thanks
Hari
SQL Server MVP
"Pawel Mylka" <pawel.mylka@.itcontrol.pl> wrote in message
news:eEnOZij4FHA.252@.TK2MSFTNGP15.phx.gbl...
> Hello,
> I have win 2k3 standard edition, 4 GB of memory, SQL 2000 enterprise
> edition. I have tryed to get more than 2 GB for sql. I have tryed /3GB
> swich
> with awe enabled on sql 2000 without any good result. I could said even
> situation is wors because now sql allocate maximum 1,327 GB.
> Does anyone hnow what can be wrong ?
> I have read many of support pages from MS for allocate more than 2G and
> nothing is working

> regards
> Pawel Mylka
>
|||Don't enable AWE unless you intend to go beyond 3GB.
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:OoI%23Nzt4FHA.3876@.TK2MSFTNGP09.phx.gbl...
> Hi,
> As Mike pointed out use Performance monitor to view the memory usage. As
> well as make the memory static (set min and max meory)
> once you enable AWE to SQL Server.
> Thanks
> Hari
> SQL Server MVP
> "Pawel Mylka" <pawel.mylka@.itcontrol.pl> wrote in message
> news:eEnOZij4FHA.252@.TK2MSFTNGP15.phx.gbl...
>

boot.ini /3GB problem

regards
Pawel MylkaHi
Task manager is not the correct tool to evaluate if memory over 2 GB is
being used as it is not capable of it.
Use Windows Performance Monitor (%SystemRoot%\system32\perfmon.msc /s) to
see how much "Target Server Memory" is. It should be close to 2700 when SQL
Server is configured correctly.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Pawel Mylka" <pawel.mylka@.itcontrol.pl> wrote in message
news:eEnOZij4FHA.252@.TK2MSFTNGP15.phx.gbl...
> Hello,
> I have win 2k3 standard edition, 4 GB of memory, SQL 2000 enterprise
> edition. I have tryed to get more than 2 GB for sql. I have tryed /3GB
> swich
> with awe enabled on sql 2000 without any good result. I could said even
> situation is wors because now sql allocate maximum 1,327 GB.
> Does anyone hnow what can be wrong '
> I have read many of support pages from MS for allocate more than 2G and
> nothing is working

> regards
> Pawel Mylka
>|||Hi,
As Mike pointed out use Performance monitor to view the memory usage. As
well as make the memory static (set min and max meory)
once you enable AWE to SQL Server.
Thanks
Hari
SQL Server MVP
"Pawel Mylka" <pawel.mylka@.itcontrol.pl> wrote in message
news:eEnOZij4FHA.252@.TK2MSFTNGP15.phx.gbl...
> Hello,
> I have win 2k3 standard edition, 4 GB of memory, SQL 2000 enterprise
> edition. I have tryed to get more than 2 GB for sql. I have tryed /3GB
> swich
> with awe enabled on sql 2000 without any good result. I could said even
> situation is wors because now sql allocate maximum 1,327 GB.
> Does anyone hnow what can be wrong '
> I have read many of support pages from MS for allocate more than 2G and
> nothing is working

> regards
> Pawel Mylka
>|||Don't enable AWE unless you intend to go beyond 3GB.
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:OoI%23Nzt4FHA.3876@.TK2MSFTNGP09.phx.gbl...
> Hi,
> As Mike pointed out use Performance monitor to view the memory usage. As
> well as make the memory static (set min and max meory)
> once you enable AWE to SQL Server.
> Thanks
> Hari
> SQL Server MVP
> "Pawel Mylka" <pawel.mylka@.itcontrol.pl> wrote in message
> news:eEnOZij4FHA.252@.TK2MSFTNGP15.phx.gbl...
>

boot.ini

I have a server with 8GB RAM. The boot.ini file's section
looks like this:
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microso ft
Windows 2000 Advanced Server with Large Memory
Support" /fastdetect /PAE
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microso ft
Windows 2000 Advanced Server" /fastdetect
Presumably it should look like this:
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microso ft
Windows 2000 Advanced Server with Large Memory
Support" /fastdetect /3GB /PAE
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microso ft
Windows 2000 Advanced Server" /fastdetect
My questions:
(1) with just /PAE presumably the OS can't access 4 of
the 8GB?
(2) what is the second multi(0)disk(0)rdisk(0)partition
(1) section for? Presumably I don't need to do anything
to it?
Many thanks in advance,
Jon
Your server is set up correctly. It is usually a good idea to have the
default configuration in the boot.ini just in case something goes wrong with
the modified one.
With /PAE you can address all the RAM, ensure you have run sp_configure 'awe
enabled', 1 to enable AWE in SQL Server. This configures SQL Server to use
a totally different set of Windows APIs to access memory.
I do not recommend using /3GB. This is required if you are not using AWE.
It also removes some memory resources from the OS. I have seen this cause
problems.
Hope this has helped.
Regards
Barry McAuslin
Look inside your SQL Server files with SQL File Explorer.
Go to http://www.sqlfe.com for more information.
"Jon" <anonymous@.discussions.microsoft.com> wrote in message
news:523701c4c8c7$2aa48a50$a401280a@.phx.gbl...
> I have a server with 8GB RAM. The boot.ini file's section
> looks like this:
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microso ft
> Windows 2000 Advanced Server with Large Memory
> Support" /fastdetect /PAE
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microso ft
> Windows 2000 Advanced Server" /fastdetect
> Presumably it should look like this:
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microso ft
> Windows 2000 Advanced Server with Large Memory
> Support" /fastdetect /3GB /PAE
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microso ft
> Windows 2000 Advanced Server" /fastdetect
> My questions:
> (1) with just /PAE presumably the OS can't access 4 of
> the 8GB?
> (2) what is the second multi(0)disk(0)rdisk(0)partition
> (1) section for? Presumably I don't need to do anything
> to it?
> Many thanks in advance,
> Jon
>
|||Barry,
this is extremely helpful - thank you.
I now understand the /PAE bit, but the 2 entries in the
boot.ini file still escapes me. Is only the first one
used? Is the second one there so someone can replace the
first with the second in safe recovery and then reboot?
Or can the second one be used automatically?
Thanks,
Jon
|||Jon
In the boot.ini file there is also an entry called timeout. If this is set
to 0 the first one in the list will be used straight away. However if the
time is say 10, you will get to choose which one you would like to boot
windows with. If you do not select an item, the first one will be used when
10 seconds is up.
I alway like to leave both entries there in case things go wrong with the
server and you want to turn /PAE off. You just select a different item from
the list.
You can also change which one is used from system properties (right click My
Computer, and select Properties). Select Startup and Recovery from the
Advanced tab.
Regards
Barry McAuslin
Look inside your SQL Server files with SQL File Explorer.
Go to http://www.sqlfe.com for more information.
"Jon" <anonymous@.discussions.microsoft.com> wrote in message
news:077c01c4c99b$6fd461c0$a501280a@.phx.gbl...
> Barry,
> this is extremely helpful - thank you.
> I now understand the /PAE bit, but the 2 entries in the
> boot.ini file still escapes me. Is only the first one
> used? Is the second one there so someone can replace the
> first with the second in safe recovery and then reboot?
> Or can the second one be used automatically?
> Thanks,
> Jon
>
|||Barry - many thanks.

>--Original Message--
>Jon
>In the boot.ini file there is also an entry called
timeout. If this is set
>to 0 the first one in the list will be used straight
away. However if the
>time is say 10, you will get to choose which one you
would like to boot
>windows with. If you do not select an item, the first
one will be used when
>10 seconds is up.
>I alway like to leave both entries there in case things
go wrong with the
>server and you want to turn /PAE off. You just select a
different item from
>the list.
>You can also change which one is used from system
properties (right click My
>Computer, and select Properties). Select Startup and
Recovery from the
>Advanced tab.
>Regards
>Barry McAuslin
>----
--
>--
>Look inside your SQL Server files with SQL File Explorer.
>Go to http://www.sqlfe.com for more information.
>"Jon" <anonymous@.discussions.microsoft.com> wrote in
message
>news:077c01c4c99b$6fd461c0$a501280a@.phx.gbl...
>
>.
>

boot.ini

I have a server with 8GB RAM. The boot.ini file's section
looks like this:
multi(0)disk(0)rdisk(0)partition(1)\WINN
T="Microsoft
Windows 2000 Advanced Server with Large Memory
Support" /fastdetect /PAE
multi(0)disk(0)rdisk(0)partition(1)\WINN
T="Microsoft
Windows 2000 Advanced Server" /fastdetect
Presumably it should look like this:
multi(0)disk(0)rdisk(0)partition(1)\WINN
T="Microsoft
Windows 2000 Advanced Server with Large Memory
Support" /fastdetect /3GB /PAE
multi(0)disk(0)rdisk(0)partition(1)\WINN
T="Microsoft
Windows 2000 Advanced Server" /fastdetect
My questions:
(1) with just /PAE presumably the OS can't access 4 of
the 8GB?
(2) what is the second multi(0)disk(0)rdisk(0)partition
(1) section for? Presumably I don't need to do anything
to it?
Many thanks in advance,
JonYour server is set up correctly. It is usually a good idea to have the
default configuration in the boot.ini just in case something goes wrong with
the modified one.
With /PAE you can address all the RAM, ensure you have run sp_configure 'awe
enabled', 1 to enable AWE in SQL Server. This configures SQL Server to use
a totally different set of Windows APIs to access memory.
I do not recommend using /3GB. This is required if you are not using AWE.
It also removes some memory resources from the OS. I have seen this cause
problems.
Hope this has helped.
Regards
Barry McAuslin
----
--
Look inside your SQL Server files with SQL File Explorer.
Go to http://www.sqlfe.com for more information.
"Jon" <anonymous@.discussions.microsoft.com> wrote in message
news:523701c4c8c7$2aa48a50$a401280a@.phx.gbl...
> I have a server with 8GB RAM. The boot.ini file's section
> looks like this:
> multi(0)disk(0)rdisk(0)partition(1)\WINN
T="Microsoft
> Windows 2000 Advanced Server with Large Memory
> Support" /fastdetect /PAE
> multi(0)disk(0)rdisk(0)partition(1)\WINN
T="Microsoft
> Windows 2000 Advanced Server" /fastdetect
> Presumably it should look like this:
> multi(0)disk(0)rdisk(0)partition(1)\WINN
T="Microsoft
> Windows 2000 Advanced Server with Large Memory
> Support" /fastdetect /3GB /PAE
> multi(0)disk(0)rdisk(0)partition(1)\WINN
T="Microsoft
> Windows 2000 Advanced Server" /fastdetect
> My questions:
> (1) with just /PAE presumably the OS can't access 4 of
> the 8GB?
> (2) what is the second multi(0)disk(0)rdisk(0)partition
> (1) section for? Presumably I don't need to do anything
> to it?
> Many thanks in advance,
> Jon
>|||Barry,
this is extremely helpful - thank you.
I now understand the /PAE bit, but the 2 entries in the
boot.ini file still escapes me. Is only the first one
used? Is the second one there so someone can replace the
first with the second in safe recovery and then reboot?
Or can the second one be used automatically?
Thanks,
Jon|||Jon
In the boot.ini file there is also an entry called timeout. If this is set
to 0 the first one in the list will be used straight away. However if the
time is say 10, you will get to choose which one you would like to boot
windows with. If you do not select an item, the first one will be used when
10 seconds is up.
I alway like to leave both entries there in case things go wrong with the
server and you want to turn /PAE off. You just select a different item from
the list.
You can also change which one is used from system properties (right click My
Computer, and select Properties). Select Startup and Recovery from the
Advanced tab.
Regards
Barry McAuslin
----
--
Look inside your SQL Server files with SQL File Explorer.
Go to http://www.sqlfe.com for more information.
"Jon" <anonymous@.discussions.microsoft.com> wrote in message
news:077c01c4c99b$6fd461c0$a501280a@.phx.gbl...
> Barry,
> this is extremely helpful - thank you.
> I now understand the /PAE bit, but the 2 entries in the
> boot.ini file still escapes me. Is only the first one
> used? Is the second one there so someone can replace the
> first with the second in safe recovery and then reboot?
> Or can the second one be used automatically?
> Thanks,
> Jon
>|||Barry - many thanks.

>--Original Message--
>Jon
>In the boot.ini file there is also an entry called
timeout. If this is set
>to 0 the first one in the list will be used straight
away. However if the
>time is say 10, you will get to choose which one you
would like to boot
>windows with. If you do not select an item, the first
one will be used when
>10 seconds is up.
>I alway like to leave both entries there in case things
go wrong with the
>server and you want to turn /PAE off. You just select a
different item from
>the list.
>You can also change which one is used from system
properties (right click My
>Computer, and select Properties). Select Startup and
Recovery from the
>Advanced tab.
>Regards
>Barry McAuslin
>----
--
>--
>Look inside your SQL Server files with SQL File Explorer.
>Go to http://www.sqlfe.com for more information.
>"Jon" <anonymous@.discussions.microsoft.com> wrote in
message
>news:077c01c4c99b$6fd461c0$a501280a@.phx.gbl...
>
>.
>

boot.ini

I have a server with 8GB RAM. The boot.ini file's section
looks like this:
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
Windows 2000 Advanced Server with Large Memory
Support" /fastdetect /PAE
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
Windows 2000 Advanced Server" /fastdetect
Presumably it should look like this:
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
Windows 2000 Advanced Server with Large Memory
Support" /fastdetect /3GB /PAE
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
Windows 2000 Advanced Server" /fastdetect
My questions:
(1) with just /PAE presumably the OS can't access 4 of
the 8GB?
(2) what is the second multi(0)disk(0)rdisk(0)partition
(1) section for? Presumably I don't need to do anything
to it?
Many thanks in advance,
JonYour server is set up correctly. It is usually a good idea to have the
default configuration in the boot.ini just in case something goes wrong with
the modified one.
With /PAE you can address all the RAM, ensure you have run sp_configure 'awe
enabled', 1 to enable AWE in SQL Server. This configures SQL Server to use
a totally different set of Windows APIs to access memory.
I do not recommend using /3GB. This is required if you are not using AWE.
It also removes some memory resources from the OS. I have seen this cause
problems.
Hope this has helped.
Regards
Barry McAuslin
----
--
Look inside your SQL Server files with SQL File Explorer.
Go to http://www.sqlfe.com for more information.
"Jon" <anonymous@.discussions.microsoft.com> wrote in message
news:523701c4c8c7$2aa48a50$a401280a@.phx.gbl...
> I have a server with 8GB RAM. The boot.ini file's section
> looks like this:
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
> Windows 2000 Advanced Server with Large Memory
> Support" /fastdetect /PAE
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
> Windows 2000 Advanced Server" /fastdetect
> Presumably it should look like this:
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
> Windows 2000 Advanced Server with Large Memory
> Support" /fastdetect /3GB /PAE
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
> Windows 2000 Advanced Server" /fastdetect
> My questions:
> (1) with just /PAE presumably the OS can't access 4 of
> the 8GB?
> (2) what is the second multi(0)disk(0)rdisk(0)partition
> (1) section for? Presumably I don't need to do anything
> to it?
> Many thanks in advance,
> Jon
>|||Barry,
this is extremely helpful - thank you.
I now understand the /PAE bit, but the 2 entries in the
boot.ini file still escapes me. Is only the first one
used? Is the second one there so someone can replace the
first with the second in safe recovery and then reboot?
Or can the second one be used automatically?
Thanks,
Jon|||Jon
In the boot.ini file there is also an entry called timeout. If this is set
to 0 the first one in the list will be used straight away. However if the
time is say 10, you will get to choose which one you would like to boot
windows with. If you do not select an item, the first one will be used when
10 seconds is up.
I alway like to leave both entries there in case things go wrong with the
server and you want to turn /PAE off. You just select a different item from
the list.
You can also change which one is used from system properties (right click My
Computer, and select Properties). Select Startup and Recovery from the
Advanced tab.
Regards
Barry McAuslin
----
--
Look inside your SQL Server files with SQL File Explorer.
Go to http://www.sqlfe.com for more information.
"Jon" <anonymous@.discussions.microsoft.com> wrote in message
news:077c01c4c99b$6fd461c0$a501280a@.phx.gbl...
> Barry,
> this is extremely helpful - thank you.
> I now understand the /PAE bit, but the 2 entries in the
> boot.ini file still escapes me. Is only the first one
> used? Is the second one there so someone can replace the
> first with the second in safe recovery and then reboot?
> Or can the second one be used automatically?
> Thanks,
> Jon
>|||Barry - many thanks.
>--Original Message--
>Jon
>In the boot.ini file there is also an entry called
timeout. If this is set
>to 0 the first one in the list will be used straight
away. However if the
>time is say 10, you will get to choose which one you
would like to boot
>windows with. If you do not select an item, the first
one will be used when
>10 seconds is up.
>I alway like to leave both entries there in case things
go wrong with the
>server and you want to turn /PAE off. You just select a
different item from
>the list.
>You can also change which one is used from system
properties (right click My
>Computer, and select Properties). Select Startup and
Recovery from the
>Advanced tab.
>Regards
>Barry McAuslin
>----
--
>--
>Look inside your SQL Server files with SQL File Explorer.
>Go to http://www.sqlfe.com for more information.
>"Jon" <anonymous@.discussions.microsoft.com> wrote in
message
>news:077c01c4c99b$6fd461c0$a501280a@.phx.gbl...
>> Barry,
>> this is extremely helpful - thank you.
>> I now understand the /PAE bit, but the 2 entries in the
>> boot.ini file still escapes me. Is only the first one
>> used? Is the second one there so someone can replace the
>> first with the second in safe recovery and then reboot?
>> Or can the second one be used automatically?
>> Thanks,
>> Jon
>
>.
>

Friday, February 10, 2012

BOOT.INI File for 4GB RAM and SQL 2005

BOOT.INI File for 4GB RAM and SQL 2005

Boot.ini file

Boot.ini file

boot.ini /3GB problem

boot.ini /3GB problem

boot.ini /3GB problem

boot.ini

boot.ini

boot.ini

Boot.ini file

Blog Archive

About Me