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.

 All Forums
 SQL Server 2000 Forums
 SQL Server Development (2000)
 Memory Leaks and CFMX

Author  Topic 

cmaso
Starting Member

5 Posts

Posted - 2005-03-04 : 18:13:20
I have ColdFusion MX and SQL Server 2000 running on the same WIN 2003 Server. We run a pretty query intensive site, and we've had problems with SQL Server memory leaks for some time. Stopping and restarting SQL Server seems to reset it, but looking at the performance monitor over the course of 24 hours, you can watch the total server memory creeping up toward the target server memory.

I've been told that this has to do with our site's code, specifically SQL queries, and I'm trying to educate myself on what the best coding practices are to prevent these leaks. I'm not sure where to start - I've always tried to build efficient queries, but I inherited this site and I'm not even sure what kinds of bad coding would cause leaks. Can anyone give me some tips, or point me in the right direction? Thanks...

TimS
Posting Yak Master

198 Posts

Posted - 2005-03-04 : 18:34:39
Is there a reason you think it is memory leaks instead of just the fact that SQL servers tend to take all the memory it can.
Have you tried to limit how much memory the SQL Server can take?

Tim S
Go to Top of Page

Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)

7020 Posts

Posted - 2005-03-04 : 18:36:15
I doubt you are really seeing a SQL Server memory leak. SQL Server is designed to take as much memory as it needs. Basically it is working the way it is designed to work. This behaviour is one reason why you should not run SQL Server and application servers on the same box.

Is this causing a problem with some other application? If so, there are options to limit the amount of memory that SQL Server uses. You can set this via the SQL Server Properties dialog, Memory tab.

However, before you do this, make sure you really have a problem, and have a thorough understanding of the way SQL Server uses memory. You should read BOL for this.


CODO ERGO SUM
Go to Top of Page
   

- Advertisement -