December 14, 2007 at 12:34 pm
Hi,
What can cause memory leak in SQL Server 2000 SP4.
Regards,
Ahmed
December 14, 2007 at 1:53 pm
if you use sp_xml_preparedocument, OPENXML, and forget sp_xml_removedocument, you will get mem leak.
Sometime though you do call sp_xml_removedocument after sp_xml_preparedocument, you can still get mem leak, e.g. time out happened before the call, or errors like PK error that returns to client immediatly and sql server doesn't have a chance to run sp_xml_removedocument
December 14, 2007 at 2:50 pm
Do you have any linked servers defined? If so, using what drivers?
I've encountered a number of memory leaks and memory scribbling coming from a DB2 driver (IA64 version)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 18, 2007 at 3:59 am
Hi,
Thanks to all.
I work for a company which developps a software to monitor SQL Server database (performance and healt), so when the software was installed in customer system, the customer complains about memory leak. After we figure out that there is no memory pressure (using performance counters: buffer hit ratio, memory pressure ratio, life expectancy, dbcc memorystatus). and now he 's complaining on CPU botleneck.
I checked in the Task manager and really sometimes the cpu usage is about 95-100 for a couple of minutes.
For the moment using the profiler, is excluded.
I used the article http://www.microsoft.com/technet/technetmag/issues/2005/05/SystemTables/ to generate a script which provide expensive processes. then I used DBCC inputbuffer(spid) to get the executed queries.
If you have any other suggestions, please let me know.
Regards,
Ahmed
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply