Re: SQL 2000 on Win2K3 Enterprise /PAE question

From: sbell (sbell_at_discussions.microsoft.com)
Date: 12/21/04


Date: Tue, 21 Dec 2004 09:23:05 -0800

I'm in a similar position. We are running SQL 2000 Enterprise on Win2K3
Enterprise. I thought that the maximum memory that could be addressed (with
PAE and AWE enabled) would be 8 GB. I'm basing this on info I found regardin
SQL on Win2K. I haven't been able to find the same data for Win2K3. Could
someone confirm the maximum memory I can address with this configuration?

"Geoff N. Hiten" wrote:

> Definitely apply the hotfix mentioned for article 834628. Another DBA here
> ran into something that he thinks may have been caused by this issue.
>
> Don't use /3GB when you have more than 12 GB of RAM in your system. The OS
> needs the extra mamory to handle mapping AWE memory back into the lower 4GB
> address space. Finally, set the MAX SERVER MEMORY to about 2-4GB less than
> your physical memory.
>
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
>
> I support the Professional Association for SQL Server
> www.sqlpass.org
>
> "Larry Kippenhan" <lwkthrowaway1@comcast.net> wrote in message
> news:e$pzBY9rEHA.2128@TK2MSFTNGP10.phx.gbl...
> > I have a couple of questions that I hope y'all will be able to give me
> > some info on.
> >
> > I am installing SQL Server 2000 on a Win2K3 Enterprise server with 20GB
> > of RAM (I know, odd number), anyway, as I was searching for information
> > on enabling all of my memory, and the /PAE option, I came across a KB
> > article, #834628
> > (http://support.microsoft.com/default.aspx?scid=kb;en-us;834628), titled
> > "Data is corrupted when PAE is enabled on a Windows Server 2003-based
> > computer". I expect this machine to give the resources a pretty good
> > workout, and I was concerned about running into this issue. Has any of
> > you run into this issue? Or, how likely is it that I will experience
> > this. Microsoft suggests not installing the hotfix unless you are
> > severely affected by this bug. To me, ANY corruption counts as severe,
> > and I really don't want to have to do all of the restores, and send 400
> > people home, etc, etc, while I fix this thing. So, any info here is
> > appreciated.
> >
> > Second question I had was: with the /PAE option, and awe enabled on the
> > SQL Server, it consumed as much of the available memory as it could
> > (about 19.7 GB). This in itself doesn't bother me, but what had me
> > puzzled, was that it appeared to be using the memory that was below the
> > 4GB line. I really expected that it wouldn't since I hadn't used the
> > /3GB switch. Any thoughts on this? Is /3GB not needed anymore, or is
> > my understanding not in line with reality?
> >
> > Thanks again for your insights.
> >
> > Larry
>
>
>



Relevant Pages

  • Re: Locking pages in memory
    ... the account SQL runs under) the permission to lock pages in memory. ... Server Standard, Enterprise, and Developer editions: Required for SQL Server ...
    (microsoft.public.sqlserver.setup)
  • Re: Worker Threads
    ... In order to use more than 4GB of memory you must use AWE. ... One is you must have Enterprise Edition of SQL ... set in the Boot.ini and AWE enabled in SQL Server. ...
    (microsoft.public.sqlserver.setup)
  • Re: Inexplicable slowdowns
    ... I profiled the SQL operation and it is taking no time at all. ... I also noticed that the server was operating at the end of available physical memory and as a result of perfmon monitoring, I saw that these slowdowns occur when the available physical memory dips to 100mb or so. ... I think SQL server is the culprit. ... It's set to consume a max of 3GB. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: FTS Performance in SQL 2005
    ... Looking for a SQL Server replication book? ... The Memory Usage and VM Size never increase over about 65 MB and 20MB. ... Can you post you query plans and the output of statistics IO ... cost relative to the whole batch, ...
    (microsoft.public.sqlserver.fulltext)
  • Re: SBS 2003 SP2 Memory
    ... MY PF is up to 4.75GB and free Physical memory is at 1.8GB. ... about the SQL instances and watching their individual need over time. ... part if your server rarely uses the pagefile. ... each of them based on usage so watch their RAM usage for a week or more and ...
    (microsoft.public.windows.server.sbs)