| SQL Server 2012 : Using XML Data - FOR XML (part 2) - Raw |
| FOR XML RAW is similar to FOR XML AUTO but with several differences. First, FOR XML AUTO does not enable you to alter the name of the elements in the resulting XML. Also, as you saw in the previous section, FOR XML AUTO names the elements after the name of the table or alias. |
|
| SQL Server 2012 : Using XML Data - FOR XML (part 1) - Auto |
| The AUTO directive is the easiest of the directives to use in which to generate XML output from results specified in the SELECT statement. Although it is certainly the easiest of the directives to use, it doesn't provide a lot of control over the resulting structure of the XML output. |
|
| SQL Server 2012 : Using XML Data - XML Data Type Methods |
| The XML data type supports a number of methods providing various operations on the XML document. An operation on an XML document is applied to one or more elements or attributes at a specific location. To perform an operation, the location of the specific element needs to be specified. |
|
|
|
|
|
| SQL Server 2012 : The XML Data Type (part 1) |
| Prior to SQL Server 2008, it was the responsibility of the application layer to produce the XML, and there was no consistent or defined way to produce the XML. Typically, it would use the XML API functions available in the programming languages to produce the desired XML, and if you have done it, it wasn't easy. |
|
|
|
|
|
|
|
|
|
| SQL Server 2012 : Query Processing - Parsing, Algebrizing |
| Query processing is performed by the Relational Engine in SQL Server. It is the process of taking the T-SQL statements you write and converting them into something that can make requests to the Storage Engine and retrieve the results needed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
