March 13, 2015 at 12:13 am
Comments posted to this topic are about the item Secondary XML Indexes
March 13, 2015 at 2:32 am
Nice question, thanks.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
March 13, 2015 at 3:48 am
This was removed by the editor as SPAM
March 13, 2015 at 5:40 am
I must admit that I don't use XML very much. It's does store very flexible data structure, but it just doesn't perform well. Thanks for the question.
March 13, 2015 at 6:06 am
Thanks for the question, Steve.
---------------
Mel. 😎
March 13, 2015 at 7:23 am
Nice question, thanks
March 13, 2015 at 9:22 am
Simple and nice. Thanks, Steve!
March 14, 2015 at 11:47 am
Nice and simple. But I avoid XML like the plague.
Tom
March 14, 2015 at 11:57 am
Ed Wagner (3/13/2015)
I must admit that I don't use XML very much. It's does store very flexible data structure, but it just doesn't perform well. Thanks for the question.
TomThomson (3/14/2015)
Nice and simple. But I avoid XML like the plague.
Heh... ditto those especially Tom's. A better question would be why would anyone in their right mind store XML in a database ever?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2015 at 12:26 pm
Jeff Moden (3/14/2015)
Ed Wagner (3/13/2015)
I must admit that I don't use XML very much. It's does store very flexible data structure, but it just doesn't perform well. Thanks for the question.TomThomson (3/14/2015)
Nice and simple. But I avoid XML like the plague.Heh... ditto those especially Tom's. A better question would be why would anyone in their right mind store XML in a database ever?
Actually there can be good reasons to store XML in a database - just as there can be reasons to store text strings. I imagine that Neos Interactive is now storing XAML in SQL Server databases, because the Beirut team was heading that way (with encouragement from me) when I handed over all tecnical responsability to them - not that the database will be looking into the XAML, I hope, just holding it and delivering it when the presentation layer wants something like "the string used for the XYX field in the UVW screen of the RST GUI in the OPQ language as spoken in LMN coutry/region". Of course the XAML fields will be held as NVARCHAR(3600) and the database will not be aware that these fields contain values in an XML-based language, and although XML is OK when used appropriately (in this instance as part of a GUI implementation using WPF) there can be no excuse for having any XML indexes or being able to treat XML within the database as anything other than an atomic string attribute with no internal structure. We were using NVARCHAR(3600) strings of text in English, French, German, two varieties of Chinese, and Russian up to 2009 but decided to upgrade to using WPF (and hence XAML) at the same time as upgrading from SQL Server 2000 to 2008 (or 2008 R2).
Tom
March 15, 2015 at 7:53 am
Ed Wagner (3/13/2015)
I must admit that I don't use XML very much. It's does store very flexible data structure, but it just doesn't perform well. Thanks for the question.
+ 1 🙂
Thanks & Best Regards,
Hany Helmy
SQL Server Database Consultant
March 15, 2015 at 7:57 am
I was sure about 2 of them, but had to search for the 3rd type, thanx.
Thanks & Best Regards,
Hany Helmy
SQL Server Database Consultant
March 16, 2015 at 6:59 am
Thanks for the question.
March 23, 2015 at 2:15 pm
info still fresh in my head, whoo!
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply