I have received some feedback on my XML datatype presentation. Before I respond to the feedback, let me thank all who attended (even the person that used the room for an after-lunch or after-party nap :-)). The best question was judged and the book was given to Jon.
Kent (btw, thanks for all the good session summaries, please accept my corrections as a service to the community and not as criticism) wrote the following points where I would like to comment:
- For XML RAW("x") generates X instead of ROW as element name
Note: this is case-sensitive.
- For XML RAW, XSINIL will generate an XSI:NIL attribute for elements that would map for null results
It is actually FOR XML RAW, ELEMENTS XSINIL
- FOR XML PATH. ok, this is trippy. I need to post on this
See http://sqljunkies.com/WebLog/mrys/archive/2004/02/20/1225.aspx
- Talked about OpenXML2 integrates natively with XML Type
Not correct: There is no OpenXML2 in Yukon (use nodes() method). I mentioned standards work that will lead to something like OpenXML on an XML datatype in a future release.
- MSXML3 is the underlying engine with Yukon
Clarification: MSXML3 is underlying OpenXML in Yukon (as it does in the 64-bit SQL Server 2000 version). MSXML 3 is not used for the XML datatype.
- Full-Text search treats identifiers as word bounds these are removed. There as a note that was that attributes are removed from the indexing model. Does that the mean just the attribute name or both the name and the value.
It means both attribute names and values.
Kent, also many thanks for correcting the SQLXML and XML dt relationship (see also my earlier post on this). I hope your hat was tasty :-).
I will add to this, when I find other feedback.
Since several people (including Kent) asked for the samples, I posted them here.