2003 memory leaks/running out of memory

[DawnP]

Hi

Can somebody help me out with a problem I am experiencing? System is running out of memory.

Customer is using 2003 which should not experience these types of memory errors. Is there a sys admin feature

In 2003 that can help isolate problem.

Here is what event viewer is logging. I have Googled the error and have run some of the suggested utilities to help isolate the problem but don’t know how to interpret the results. I ran (memTriage and VaDump). MemTriage flagged four processes that are using more than 80% of Virtual Address Space:

sqlserver.exe 135140(K)
NTRtscan.exe 60080(K)
w3wp.exe 27720(K)
iexplore.exe 16528(K)
svchost.exe 16496(K)
I then ran VaDump on the process id associated with sqlserver but I don't know how to interpret the results. I also loaded the Resource Tools for Windows 2003 Server and ran Pmon.exe but again, not sure how to interpret the results. I have an HP Proliant ML350 with 2 GB of memory running Windows 2003 R2 with SP 2 running SQL 2000 and a time keeping application. Thanks.....Dawn

Event ID: 2019
Source: Svr
Version: 5.2
Symbolic Name: Event_Srv_No_Nonpaged_Pool
Message: The server was unable to allocate from the system nonpaged pool because the pool was empty.

 

[mrdenny]

Well, your problem is going to be that SQL Server by default will take all the memory on the server. You need to log into the server and tell SQL Server the limit the max amount of memory that it can use. With a 2 Gig server you should leave at least 512 MB for the OS. If you need more than that for Windows and the other things running on the server then try lowering the max memory to 1024 MB.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

My Blog

 

[itsp1965]

As far as i recall this is not entirely true. SQL server will use as much as possible but will cap out at 2GB since it will not take away all memory required by the OS.
It is quite possible that other apps/processes are taking up memory. Check the task manager to see how the memory is being used up. It is possible that you may need to increase the size of the pagefile for your system (if you have the space let Windows set it for you) and if possible add more memory.
Hope this helps.

 

[mrdenny]

I have an HP Proliant ML350 with 2 GB of memory running

SQL will use all of that.

SQL 2000 Standard Edition will stop at 2 Gigs. Enterprise / Developer will take all the memory (if AWE is enabled on a 32bit system).

With SQL 2005 Standard Edition will take all available memory (with AWE enabled to get past 2 Gigs).

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

My Blog

 

[DawnP]

Hi thanks for the info. We are using SQL 2000 Standard Edition. Where in SQL do I set the limit for memory usage? I already tried letting Windows manage the Pagefile as well as move it to a different drive but that did not work...Dawn

 

[mrdenny]

Open the Enterprise Manager, right click on the server and select properties at the bottom, and go to the memory tab.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

My Blog