"kunalap" <kuna***@discussions.microsoft.com> wrote in message
news:679ACD2F-5264-4E4B-84DF-8FD5DAA0B795@microsoft.com...
> Hi,
> I have a server where their ASP menu page running recusive queries takes a
> long time to load.
>
> We have created indexes as per queries in the menu page and now are
> looking
> at setting SQL Server to use 3GB out of the 4GB memory available on the
> server.
>
> For this to be done, I need to:
> 1. Grant 'lock pages in memory' rights to out SQL server startup service
> account
> 2. Set AWE setting in SQL Server to 3GB
>
> Is this correct ? Or are there any other steps to be taken? No changes to
> boot.ini, right?
>
> Also, the current default value for max memory in SSMS is 2147483647. What
> would be the value for 3GB?
>
> Cheers.
>

"Uri Dimant" wrote:

> Hi
> Is it 64 bit or 32? In 64 bit you do no need AWE if I remember well.
>
>
> If you are using SQL Server 2005 to configure memory to use more than 2 GB
> of physical, see the following topics in SQL Server 2005 Books Online:
>   a.. Memory Architecture
>   b.. Server Memory Options
>   c.. Using AWE
>   d.. Enabling Memory Support for Over 4 Gb of Physical Memory
>   e.. Enabling AWE Memory for SQL Server
>
>
>
>
> "kunalap" <kuna***@discussions.microsoft.com> wrote in message
> news:679ACD2F-5264-4E4B-84DF-8FD5DAA0B795@microsoft.com...
> > Hi,
> > I have a server where their ASP menu page running recusive queries takes a
> > long time to load.
> >
> > We have created indexes as per queries in the menu page and now are
> > looking
> > at setting SQL Server to use 3GB out of the 4GB memory available on the
> > server.
> >
> > For this to be done, I need to:
> > 1. Grant 'lock pages in memory' rights to out SQL server startup service
> > account
> > 2. Set AWE setting in SQL Server to 3GB
> >
> > Is this correct ? Or are there any other steps to be taken? No changes to
> > boot.ini, right?
> >
> > Also, the current default value for max memory in SSMS is 2147483647. What
> > would be the value for 3GB?
> >
> > Cheers.
> >
>
>
>

"kunalap" wrote:

> Its a 32bit machine with SQL 2005. SQL currently uses only 1.7GB as per
> default setting.
>
>
> "Uri Dimant" wrote:
>
> > Hi
> > Is it 64 bit or 32? In 64 bit you do no need AWE if I remember well.
> >
> >
> > If you are using SQL Server 2005 to configure memory to use more than 2 GB
> > of physical, see the following topics in SQL Server 2005 Books Online:
> >   a.. Memory Architecture
> >   b.. Server Memory Options
> >   c.. Using AWE
> >   d.. Enabling Memory Support for Over 4 Gb of Physical Memory
> >   e.. Enabling AWE Memory for SQL Server
> >
> >
> >
> >
> > "kunalap" <kuna***@discussions.microsoft.com> wrote in message
> > news:679ACD2F-5264-4E4B-84DF-8FD5DAA0B795@microsoft.com...
> > > Hi,
> > > I have a server where their ASP menu page running recusive queries takes a
> > > long time to load.
> > >
> > > We have created indexes as per queries in the menu page and now are
> > > looking
> > > at setting SQL Server to use 3GB out of the 4GB memory available on the
> > > server.
> > >
> > > For this to be done, I need to:
> > > 1. Grant 'lock pages in memory' rights to out SQL server startup service
> > > account
> > > 2. Set AWE setting in SQL Server to 3GB
> > >
> > > Is this correct ? Or are there any other steps to be taken? No changes to
> > > boot.ini, right?
> > >
> > > Also, the current default value for max memory in SSMS is 2147483647. What
> > > would be the value for 3GB?
> > >
> > > Cheers.
> > >
> >
> >
> >

"Erland Sommarskog" wrote:

> Linchi Shea (LinchiS***@discussions.microsoft.com) writes:
> >> What would be the value for 3GB?
> >
> > 3*1024 = 3072. No need to cahnge anything in boot.ini
> 
> Hm, I don't think so. Either Kunalap needs to add the /3GB switch to
> BOOT.INI, and leave AWE turned off. Or he needs to add /PAE and turn on
> AWE. Else the OS will continue to se 2GB of memory.
>
>
> --
> Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se
>
> Links for SQL Server Books Online:
> SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
> SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
> SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
>
>

"Erland Sommarskog" wrote:

> kunalap (kuna***@discussions.microsoft.com) writes:
> > Erland,
> > Why will OS see 2GB? Its a 32-bit machine, so it can see 4GB.
>
> Sorry, a typo. The last sentence should read: "Else the OS will continue
> to use 2GB of memory.". That is, "use", not "see".
>
>
>
>
> --
> Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se
>
> Links for SQL Server Books Online:
> SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
> SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
> SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
>
>

"kunalap" wrote:

> As far as I know, there is no limitation on OS to keep using 2GB.
> The limitation is only on SQL side to use 1.7GB (2GB).
> And this limitation can be broken upto 4GB limit by AWE.
>
> Beyond 4GB is a whole different story.
>
> However, I do wonder what the /3GB switch and /PAE (or something like that)
> are used for.
>
>
>
> "Erland Sommarskog" wrote:
>
> > kunalap (kuna***@discussions.microsoft.com) writes:
> > > Erland,
> > > Why will OS see 2GB? Its a 32-bit machine, so it can see 4GB.
> >
> > Sorry, a typo. The last sentence should read: "Else the OS will continue
> > to use 2GB of memory.". That is, "use", not "see".
> >
> >
> >
> >
> > --
> > Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se
> >
> > Links for SQL Server Books Online:
> > SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
> > SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
> > SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
> >
> >

"Erland Sommarskog" wrote:

> kunalap (kuna***@discussions.microsoft.com) writes:
> > As far as I know, there is no limitation on OS to keep using 2GB.
> > The limitation is only on SQL side to use 1.7GB (2GB).
>
> If the OS uses 2GB of memory, SQL Server can't use more than 1.7 GB.
>
> > And this limitation can be broken upto 4GB limit by AWE.
> >
> > Beyond 4GB is a whole different story.
> >
> > However, I do wonder what the /3GB switch and /PAE (or something like
> > that) are used for.
>
> /3GB gives you 3GB of memory for user space, and only 1GB for the OS.
> /PAE enables Physical Address Extensions, which is what AWE is all about.
> Linhci may be right in that /PAE is enabled by default in modern server
> OS:s.
> 
>
>
> --
> Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se
>
> Links for SQL Server Books Online:
> SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
> SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
> SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
>
>

"kunalap" <kuna***@discussions.microsoft.com> wrote in message
news:AE5D5EEC-56FE-4E79-8CEC-F43B1F0739BF@microsoft.com...
> Currently I don't see OS using 2GB memory.
> How do I ensure OS doesn't use 2GB memory?
>
> Since I will be setting SQL to use 3GB out of the 4GB memory, OS using
> even
> 1 GB will end up in server hanging and giving other issues.
>
>
>
> "Erland Sommarskog" wrote:
>
>> kunalap (kuna***@discussions.microsoft.com) writes:
>> > As far as I know, there is no limitation on OS to keep using 2GB.
>> > The limitation is only on SQL side to use 1.7GB (2GB).
>>
>> If the OS uses 2GB of memory, SQL Server can't use more than 1.7 GB.
>>
>> > And this limitation can be broken upto 4GB limit by AWE.
>> >
>> > Beyond 4GB is a whole different story.
>> >
>> > However, I do wonder what the /3GB switch and /PAE (or something like
>> > that) are used for.
>>
>> /3GB gives you 3GB of memory for user space, and only 1GB for the OS.
>> /PAE enables Physical Address Extensions, which is what AWE is all about.
>> Linhci may be right in that /PAE is enabled by default in modern server
>> OS:s.
>>
>>
>>
>> --
>> Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se
>>
>> Links for SQL Server Books Online:
>> SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
>> SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
>> SQL 2000:
>> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
>>
>>

"Erland Sommarskog" wrote:

> Linchi Shea (LinchiS***@discussions.microsoft.com) writes:
> >> What would be the value for 3GB?
> >
> > 3*1024 = 3072. No need to cahnge anything in boot.ini
> 
> Hm, I don't think so. Either Kunalap needs to add the /3GB switch to
> BOOT.INI, and leave AWE turned off. Or he needs to add /PAE and turn on
> AWE. Else the OS will continue to se 2GB of memory.
>
>
> --
> Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se
>
> Links for SQL Server Books Online:
> SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
> SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
> SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
>
>

"Linchi Shea" wrote:

> The original post didn't say that the OS could only see/use 2GB. I assumed
> the OS could see all the physical RAM. Also, these days, it's very rare to
> actually set /PAE in boot.ini as that is oftne auto-enabled in Win2K3 and
> most of the servers. So to more precise, as long as the OS can see all the
> physical memory, there is no need to touch boot.ini.
>
> Linchi
>
> "Erland Sommarskog" wrote:
>
> > Linchi Shea (LinchiS***@discussions.microsoft.com) writes:
> > >> What would be the value for 3GB?
> > >
> > > 3*1024 = 3072. No need to cahnge anything in boot.ini
> > 
> > Hm, I don't think so. Either Kunalap needs to add the /3GB switch to
> > BOOT.INI, and leave AWE turned off. Or he needs to add /PAE and turn on
> > AWE. Else the OS will continue to se 2GB of memory.
> >
> >
> > --
> > Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se
> >
> > Links for SQL Server Books Online:
> > SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
> > SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
> > SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
> >
> >