|
|
|
Mr or Mrs. 500
      
Group: General Forum Members
Last Login: Saturday, February 13, 2010 12:45 AM
Points: 553,
Visits: 18
|
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Thursday, May 16, 2013 1:28 PM
Points: 15,
Visits: 43
|
|
I work since a few months with XML and I found very useful this article because I didn´t know all the advantages mencioned in the article. Thanks and sorry for my english (I'm from Argentina).
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Thursday, August 09, 2007 10:18 PM
Points: 6,
Visits: 1
|
|
| This was a very useful article. What is the size limit to the VARCHAR(max) declaration?
|
|
|
|
|
Old Hand
      
Group: General Forum Members
Last Login: Yesterday @ 1:35 PM
Points: 301,
Visits: 473
|
|
Nice. the difference in time is more pronounced at 40k rows than 20k, although if you keep going up the time to create the delimited string becomes too unbearable to test. Question: assuming that the delimited string is coming from the outside (so you don't have to worry about the time to create it), will there be a point at which the performance of the REPLACE() function becomes unbearable also? Small thing: You probably need to change your name for the XML proc in the code sample and also your test code, which does this: print @CSV exec usp_LoopVersion @CSV exec usp_LoopVersion @CSV Thanks, >L<
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Thursday, October 21, 2010 6:46 AM
Points: 25,
Visits: 5
|
|
XML is a good solution for some sticky problems. For example, I'm programming an application that stores information for physical exams that a medical practice performs. The problem is that the exam is rather dynamic, in that it frequently changes (doctors are a contentious breed), and updating the database was becoming a real challenge because of the necessity of keeping old data and new data in the same tables. The solution was to store the raw exam data in an XML field, but keep basic patient information (ExamID, DateOfService, ExamType, etc) in regular SQL Server fields. That way I could retrieve the XML field, then query and update it using XML classes directly from my windows application. The good news is that if the XML node isn't present, the XML query simply ignores that part of the query without breaking the code. In other words, the structure of the exam can change without blowing up the application or requiring major changes in my existing functions in the data layer. Really nice. Lee...
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Wednesday, December 19, 2012 9:30 PM
Points: 1,032,
Visits: 388
|
|
2,147,483,647 bytes, basically 2 Gigabytes
/*****************
If most people are not willing to see the difficulty, this is mainly because, consciously or unconsciously, they assume that it will be they who will settle these questions for the others, and because they are convinced of their own capacity to do this. -Friedrich August von Hayek
*****************/
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Thursday, February 21, 2013 8:55 AM
Points: 219,
Visits: 807
|
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Wednesday, March 26, 2008 9:54 AM
Points: 1,
Visits: 8
|
|
Well it was great article for the developers who want to know about the advantages of XML in SQL SERVER 2005. Regards Mian Rehmat Local Govt, UK.
|
|
|
|