November 9, 2005 at 4:47 am
I have an application that slows down with little usuage that slows down throughout the day.
The developers have squarely put this down to a memory leak with the boss!
its now at my door to locate or prove that this is not the case,
im on 2000 with sp3, where should i start looking?
November 9, 2005 at 6:37 am
Start with getting network engineers and server engineers involved to start sniffing network/mem usage
start running profiler to capture what is going on.
Have someone else (other than the original developer(s)) look at the application for improvement
Good Hunting!
AJ Ahrens
webmaster@kritter.net
November 10, 2005 at 12:57 am
Are they saying that the problem is caused by a memory leak in SQL Server or the application (which I suspect they wrote)? If the former, how would they know that? If the latter, why should you look in SQL Server to prove this?
November 10, 2005 at 2:01 am
As a developer of software for use in-house, I'd agree with what I think is Chris's subtext - if there were SQL Server memory leaks we'd be likely to know by now. Much more probable is either gradual resource consumption by bad programming (eg not dropping database connections or not collecting other high-level garbage) or by the bad-but-understandable stuff that nasty, dirty languages like VC++ (I can feel the flames starting to lick around my feet!) can get even the wary into.
If the app slows during the working day, what happens when the leaked memory is recovered? Does this happen due to reboots or service restarts, or client side restarts? Even if the recovery is after the restart of SQL Server, the app may still be at fault.
Your developer team might want to look into the tools Compuware DevPartner (and its competitors) provide for getting to the bottom this kind of thing. An independent code review might be a good idea - we have previously done this (on another platform) and rather than spend weeks fixing the individual problem, the consultant was able to point out bad practice in a day or two. When we fixed the bad practice, the problems went away.
Good luck.
Bill.
November 10, 2005 at 10:14 am
watch the memory variation on sqlserver.exe process it may help you
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply