Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2006-02-23 : 09:08:37
|
| Nathan writes "We are currently running a number of SQL Servers and, for the most part, having little trouble with prerformance. However, we do have 1 SQL Server that seems to have a chronic memory leak problem. The server will run for about a week at a time before it runs out of memory and begins rejecting requests from users due to "Not Enough Memory to Complete Request". At this point, the only thing we can do is reboot the server to release all the cached memory. My question is, do you know of a logical methodology for diagnosing such a problem? I imagine there is a rogue Stored Procedure or an application problem (ASP .net) that is doing something to tie up memory and not releasing it, I'm just not sure how or where to beging looking for it.Here's what I can tell you about the SQL Server:HP Proliant DL380 G32 3.2 GIG processors3 GIG memoryWindows 2003 SP1SQL 2000 Standard SP4 + hotfixes. version 8.00.2162Any help you can offer will be greatly appreciated.Best Regards,Nathan C. HoialmenMinneapolis, MN" |
|
|
RickD
Slow But Sure Yak Herding Master
3608 Posts |
Posted - 2006-02-23 : 10:11:32
|
| Put a trace on the server to see which application is making all the calls and not releasing memory.. |
 |
|
|
|
|
|
SQL Server Memory Leak