DAT319 XML in the Database - the XML Data Type in SQL Server 2005 (code named "Yukon")
Got to this very late thanks for a very interesting lunch I enjoyed with Levi
Erdmann (State of ND) and Jenni French of MS.Com. Michael, if you are reading
this, could you send me or post your examples?
- XML Index
- XML Primary is on XML typed column
- XML Secondary indices on elements and attributes
- XML Data Modification
- Standard CRUD is support for XML typed columns
- FOR XML Examples
- Showed Linked view of XML Type
- For XML RAW("x") generates X instead of ROW as element name
- For XML RAW, ELEMENTS generates element-centric XML
- For XML RAW, XSINIL will generate an XSI:NIL attribute for elements
that would map for null results
- For XML RAW, TYPE generates true XML data type instance
- For XML AUTO now supports recursive query select * (select * from
orders where orders.customerid=customer.customerid.id for xml auto,
type) from customers for xml auto, type
- FOR XML EXPLICIT (query from hell mode) still uses universal table
approach
- FOR XML PATH. ok, this is trippy. I need to post on this
- The FOR XML Aggregator accepts a row and other directions and generates
the XML and spits back the results
- FOR XML is fully backward comptabile, timestamps will be serialized
differently
- Talked about OpenXML2 integrates natively with XML Type
- MSXML3 is the underlying engine with Yukon
- 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.
- Full-text supports language
- XML Data Access, SQLOLEDB is either a string on ISequentialStream; COM
(ADO,
- Managed code gets XML type if data is returned that way
- SQLXML and SQLSOAP turn XML Character Stream.
- XML Data type support fully supports data binding in ADO.NET 2.
Through presentation, but quickly paced. You're really going to have make all
of these presentations to appreciate what's in play here.