RE: Memory Problems



Hey Steven - also you may want to start a Profiler Trace & capture that info
there to get to what is happening inside SQL that may be causing you pain. I
agree with Brant too about giving it the extra gig by using the /3gb switch.

"Brant" wrote:

> Steven-
> a) when SQL server reaches its 2 gig memory limit, sql will have to
> reevaluate the way it is using memory, and make adjustments accordingly.
> Performance could degrade, but it shouldnt bring the server to its knees
> b) in PerfMon, look under SQL Server:Memory Manager. here you will find
> counters such as connection memory, lock memory, SQL cache memory, optimizer
> memory. It is a good idea to baseline your server with Perfmon before your
> issue occurs, so that you have something to compare the results to.
> c) i would hold off on upgrading to EE until you have an understanding of
> how SQL is currently using your memory.
>
> It might benefit you to use the /3gb switch in your boot.ini to gain an
> extra gig of memory that sql can use.
>
>
> Hope this helps,
>
> Brant
>
>
> "Steven Clark" wrote:
>
> > I have a server which is running with 4 gig ram, quad xeon on windows 2000
> > server with SQL Standard edition. It appears that SQL is taking all the
> > memory it possibly can (approx 2gig) from the system and then when it cant
> > take any more, it slows down its functioning almost to a stop.
> >
> > Can anyone answer any of these questions I have:
> >
> > a) I know standard edition has a 2 gig memory limit, what happens when it
> > reaches that point?
> > b) Is there anyway I can try and diagnose why SQL is doing this? I have
> > tried looking at performance monitor but i'm not sure what to look for.
> > c) Would upgrading to Enterprise edition possibly fix these problems or
> > would that just cause SQL to take even more system memory?
> >
> >
> > Thank you
> >
> >
> > Steven
> >
> >
> >
.



Relevant Pages

  • Re: Performance problems -- need guidance on scaling
    ... Thanks for the update on the FT Catalog corruption, ... will use, up to a max of 512Mb, if this memory is available. ... a server with 512 MB of RAM and a resource_usage value of 5 ... the data, you could, detach your SQL 2000 mdf & ldf files ...
    (microsoft.public.sqlserver.fulltext)
  • Re: Memory Issues
    ... Exchange and SQL Server. ... you identified memory problems and large amounts of paging. ...
    (microsoft.public.sqlserver.setup)
  • Re: Memory issues with 64-bit SQL Server 2005 on 64-bit Win 2003 Clust
    ... The Paging File usage is due to how the large memory allocation APIs work. ... Swap files for SQL do not need to be more than about 2-4 GB regardless of physical memory on the box. ... If you use Performance Monitor to track actual paging activity, you will see very little on a properly tuned SQL Server. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Allocating more memory to sql server
    ... Are you sure you have Windows 2000 Advanced Server and not just Server? ... SQL Server. ... memory used by SQL Server that will give a better idea of the actual usage. ... You also need to restart SQL Server after enabling AWE for it to take ...
    (microsoft.public.sqlserver.setup)
  • Re: Memory issues with 64-bit SQL Server 2005 on 64-bit Win 2003 C
    ... Manager nusance has been around, and yet they somehow could never find time ... counter Total Server Mmeory shows 18GB. ... due to how the large memory allocation APIs work. ... Swap files for SQL do not need to be more than about 2-4 GB ...
    (microsoft.public.sqlserver.clustering)