September 3, 2014 at 4:30 am
You are correct Adam. My brain flubbed.
September 3, 2014 at 4:11 pm
Thanks for the tip, but given this:
"The MSXML parser uses one-eighth the total memory available for SQL Server. To avoid running out of memory, run sp_xml_removedocument to free up the memory."
I think I'll leave it up to XQuery, given it's not super time critical.
September 13, 2014 at 5:27 am
It is correct that it does that. However, you shouldn't be afraid to use it! Every xml document must be opened in a likewise manner. You simply need a close at the end of using it. Even with the Open/Close, it is still much faster and uses fewer server resources (reads, etc) than XQuery.
Adam Hardy-416657 (9/3/2014)
Thanks for the tip, but given this:"The MSXML parser uses one-eighth the total memory available for SQL Server. To avoid running out of memory, run sp_xml_removedocument to free up the memory."
I think I'll leave it up to XQuery, given it's not super time critical.
September 13, 2014 at 11:21 am
venoym (9/2/2014)
By the way, XQuery is tons slower than OPENQUERYXML when you need to shred unknown XML elements.
Heh... I knew what you meant and I find that VERY interesting because I've been arguing at work about that. Glad to see that someone has the same experience with that. Thanks!
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply