Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
X002548
Not Just a Number
15586 Posts |
Posted - 2007-06-21 : 09:24:32
|
We are thinking about using this sproc because one of our .NET app's is basically handling an array of data. The .NET guys want to give me 1 input parameter (i.e. XML) and then I would use the sproc to parse it and store the base data in columns.Anyone witth experience with this or any comments would be appreciatedBrett8-)Hint: Want your questions answered fast? Follow the direction in this linkhttp://weblogs.sqlteam.com/brettk/archive/2005/05/25/5276.aspxAdd yourself!http://www.frappr.com/sqlteam |
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2007-06-21 : 09:42:41
|
It’s OK for occasional use, but I would avoid it in a high volume transaction environment, because of the memory requirements.From SQL 2000 Books Online:"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."CODO ERGO SUM |
 |
|
X002548
Not Just a Number
15586 Posts |
Posted - 2007-06-21 : 11:52:15
|
Well, yerah, I read that, and managing memory...I'm not to keen on that...It's just that over lo thje many years, I rarely see any XML discussions, and maybe about 0% about that sproc....so....I was trying to make a case either for or against it's usageBrett8-)Hint: Want your questions answered fast? Follow the direction in this linkhttp://weblogs.sqlteam.com/brettk/archive/2005/05/25/5276.aspxAdd yourself!http://www.frappr.com/sqlteam |
 |
|
X002548
Not Just a Number
15586 Posts |
|
|
|
|