Introduction

The purpose of displaying data from the xml datatype in a relational form is to apply normal ADO.NET practices and other relational data management concepts easily.

• Formation of Views from this formed relational data.
• Retrieval of this data as dataset, recordset or simply raw XML again.
• This data can easily be used with multiple data providers for further processing.

Displaying XML in Relational form

Let us begin with the same Invoices XML used in part 1. Suppose we would like to display that XML in relational form as displayed below:

Then we simply execute the following code:

We can easily break the operations of the SELECT query above into two parts:

Part 1 retrieves the nodes from the Table (Column) form:

Here we retrieve all nodes from Invoices by using @xmldata .nodes('Invoices/Invoice'). We use the AS keyword to set an alias name to @xmldata as a table (Tabx), and a column(Colx).

Part 2 queries the data in the relational column.

Here we query Colx with the query method passing in an XQuery expression as the parameter. We also specify the alias name for the column with AS InvoiceId.

The CROSS APPLY clause

A CROSS APPLY is an INNER JOIN between a table and a table-valued function. This is a new feature of SQL Server 2005. The results are normally used to retrieve and display running totals. In previous version of SQL Server, the same was achieved by using a temp table.

Displaying xml datatype data in relational form

Let's assume we have a table in the database for the Purchases made by a Purchaser from many other different Sellers. Each Seller would issue a different electronic Invoice which would be stored in a raw XML form in the database and each Seller would assign different types of 'InvoiceId's, different format of dates etc. . Here, we have a table Purchases of that type with the following data.

Hence our SELECT query for this table would be:

Our result for the above query would be:

Summary

The display of XML data as relational tables becomes very important in cases where the front ends are classical in nature not supporting latest XML standards. This is also useful in the intermediate phases of an application upgrade for the easy compatibly of the phase-in components with phase-out components.

About Imran Nathani

Sorry, no bio is available This author has published 5 articles on DotNetSlackers. View other articles or the complete profile here.

---

Discussion

Subject	Author	Date
Very good article	Rajesh S	7/30/2008 6:06 AM
It was very useful imran. Thanks a lot. Great... Reply | Permanent link

---

Please login to rate or to leave a comment.