Provide a way to reclaim the memory lost by absent calls to sp_xml_removedocument - by danholmes

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 776637 Comments
Status Closed Workarounds
Type Suggestion Repros 1
Opened 1/15/2013 4:29:15 PM
Access Restriction Public


BOL states that sp_xml_preparedocument and sp_xml_removedocument should be executed in pairs.  That is good but what if there is a bug in the TSQL?  The memory is lost and there isn't a complete way to handle the problem.
Sign in to post a comment.
Posted by Elaskanator on 4/25/2017 at 9:46 AM
I managed to crash a webservice at work by making a sizable request that filled the memory pool, and the webservice did not clean up the failed XML response it was building, leaving the system memory exhausted.
Running DBCC FREESYSTEMCACHE('all'); did not reclaim the memory.
Now all subsequent calls to said webservice immediately fail because there is insufficient server memory.
Posted by Microsoft on 4/22/2013 at 5:53 AM
Thank you for submitting this feedback. After carefully evaluating all of the suggestion items in our pipeline, we are closing items that we will not implement in the near future due to current higher priority items. We will re-evaluate the closed suggestions again in the future based on the product roadmap.

Thanks again for providing the product suggestion and continued support for our product.