MSXML parser & SQL Server Memory

The below snippet from SQL Server BOL under the topic "sp_xml_preparedocument" implies that the use of XML can be extremely memory intensive. Is is really the case that MSXML uses 1/8 total SQL Server memory? I find this astounding if true.
"Note A parsed document is stored in the internal cache of SQL Server 2000. 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."
It means that it can use up to 1/8th of the memory. Unless you try to parse
a very large document or never release the allocated memory, you should
never use or reach this limit.
HTH
Michael
"glr" <glr@.discussions.microsoft.com> wrote in message
news:DE9CFF6C-B949-4318-9294-6B4EFB773AF2@.microsoft.com...
> The below snippet from SQL Server BOL under the topic
> "sp_xml_preparedocument" implies that the use of XML can be extremely
> memory intensive. Is is really the case that MSXML uses 1/8 total SQL
> Server memory? I find this astounding if true.
> "Note A parsed document is stored in the internal cache of SQL Server
> 2000. 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."
>

mssql mem usage

running mssql server 2000. experiencing extremely high mem usage - 420 000 k. Can anyone help me determine what on earth is happening? Urgent.
Appreciate any help.
tq.420MB of RAM used is no where near of being "too high". What's the total physical memory? If you have memory shortage you should set the max for SQL service (in fact you should always set the max value)|||Most of my machines run well over 2 Gb for SQL Server... 420 Mb would be heavy on a workstation (Personal Edition), but wouldn't be enough to start most of our servers.

-PatP|||420MB would be heavy on a workstation? What does it have to do with a workstation? Are you running prod environment off of it? Personal edition is for development and for occasional "select * from authors" when arguing with dbForums' bunch trying to prove the point ;)|||this is an prod environment. machine total physical memory is 523760. sqlserver.exe is using 375 000 to 420 000 k. It has been running for a year with no problems. until now...what would be the optimal value to set the max for sql?|||First, add MORE memory, at least 512MB more. With 1GB of physical memory you can set the minimum for SQL at 800MB. Since it started consuming more memory it's an indicator that some optimization needs to be performed since your volume of data increased.