XML and SQL 2000 (Part 1)

One of the most common problems with managing data is its versatility. This becomes evident when exchanging data between multiple data sources and results mainly from incompatibilities in data representation and format. The impact of this type of problem affects most companies internally, but is even more acute in the business-to-business or business to consumer scenarios. Early solutions to this problem (such as Electronic Data Interchange) have never become popular due to their high cost and limited flexibility. A breakthrough took the form of Extensible Markup Language, technology derived from Standardized General Markup Language, developed under the auspices of the World Wide Web Consortium (www.w3.org). XML is frequently compared with an SGML derivative – HTML. While HTML defines the structure of data, XML’s purpose is providing a description of the data structure. Just as with HTML, XML uses tags to accomplish this goal. However, unlike HTML, there are no fixed set of XML tags – they can be named in whatever way is best suitable for conveying the information about the data (hence the eXtensible in the “XML”).

SQL Server 2000 includes built-in support for XML. Even though some limitations of this implementation exist, conversion between relational and XML-formatted data is greatly simplified. This includes the following features:

  • retrieving relational data in XML format with FOR XML clause of the SELECT statement,
  • inserting XML data into the database with OpenXML rowset provider,
  • execute T-SQL statements queries against SQL Server via HTTP using IIS Virtual Directory Management.

Retrieving data as XML document using FOR XML clause of the SELECT statement

In order to retrieve data as an XML document, you need to modify a standard format of the SELECT statement. The level of modification depends on the options you will use with the FOR XML clause. In general, the clause takes the following format:



  • Mode can be RAW, AUTO, or EXPLICIT and determines the format of the resulting XML document. In order to understand what this means, we need to briefly describe these formats. In general, there are two ways of representing data returned as an XML document – using sub elements and attributes. For example, the following XML document consists of four sub elements:
       <Name>"Very Small Widget"</Name>

    However, it is also possible to represent the same data in the form of attributes of a single element, which would produce the following XML document:

    <InventoryItem Name="Very Small Widget" Type="Hardware" QuantityInStock=20 Price=0.49 />
    • The RAW keyword returns an XML document by presenting each row as a single element with columns as attributes. Each element is named simply “row.” This means that the following query (against Shippers table in Northwind database):
      SELECT ShipperID, CompanyName, Phone
      FROM Shippers

      would return the following result:

      <row ShipperID="1" CompanyName="Speedy Express" Phone="(503) 555-9831"/>
      <row ShipperID="2" CompanyName="United Package" Phone="(503) 555-3199"/>
      <row ShipperID="3" CompanyName="Federal Shipping" Phone="(503) 555-9931"/>

      The format of the result is the same, regardless of the number of tables referenced in the SELECT statement.

    • The result returned when AUTO keyword is used depends on whether one or more tables are being used in the query. With one table, the only effect of using AUTO keyword is the fact that the individual elements are no longer labeled “row” – instead they are named after the table, which in our example would return the following:
      <Shippers ShipperID="1" CompanyName="Speedy Express" Phone="(503) 555-9831"/>
      <Shippers ShipperID="2" CompanyName="United Package" Phone="(503) 555-3199"/>
      <Shippers ShipperID="3" CompanyName="Federal Shipping" Phone="(503) 555-9931"/>

      However, if the SELECT statement includes multiple tables, the results would return one element per table. Elements corresponding to rows of tables referenced further in the SELECT statement become sub elements of the top level elements (the level of nesting would depend on the order in which these tables appear in the SELECT statement). For example, the following query:

      SELECT ShipperID, CompanyName, OrderID
      FROM Shippers
      LEFT JOIN Orders
      ON Shippers.ShipperID = Orders.ShipVia

      Would return the following results (with majority of data omitted for clarity):

      <Shippers ShipperID="1" CompanyName="Speedy Express">
          <Orders OrderID="10249"/>
          <Orders OrderID="11071"/>
      <Shippers ShipperID="2" CompanyName="United Package">
          <Orders Order="10440"/>
          <Orders OrderID="11077"/>
      <Shippers ShipperID="3" CompanyName="Federal Shipping">
          <Orders OrderID="10248"/>
          <Orders OrderID="11061"/>
    • Data returned by the SELECT statement with the AUTO keyword can be further modified by using the ELEMENT keyword, which causes a conversion of all attributes into sub elements. By adding the ELEMENTS keyword (following a comma) at the end of the FOR XML AUTO clause in our previous example, we would get the results in the following format:
        <CompanyName>Speedy Express</CompanyName>
        <CompanyName>United Package</CompanyName>
        <CompanyName>Federal Shipping</CompanyName>
Marcin Policht
Marcin Policht
Being a long time reader, I'm proud to join the crowd of technology gurus gathered here. I have a fair share of Microsoft exams behind me, a couple of acronyms after my name - MCSE, MCSD, and MCT, decent familiarity with majority of MS BackOffice products (SMS, SQL, Exchange, IIS), programming and scripting languages (VB, C++, VBScript with wsh) and several years of practical experience with Windows environment administration and engineering. My focus these days is on SQL Server and Windows 2000, and I'll attempt to share the most interesting experiences with these products.

Get the Free Newsletter!

Subscribe to Cloud Insider for top news, trends & analysis

Latest Articles