SQL Server Reference Guide

Mar 28, 2003

␡

⎙ Print

< Back Page 240 of 365 Next >

The concepts of relational database theory and hierarchical document formats seem miles apart. But in reality, it's all just about looking at data in multiple ways.

Last week, I showed you how to use the FOR XML EXPLICIT predicate to create more powerful extracts from a database than using FOR XML AUTO. This week, I explain how to break relational data into hierarchies. Hierarchies are natural outputs of XML.

I've chosen a simple example. I want a list of authors and the books each author has written. I'll publish this list out to an advertiser. The advertiser wants to see the authors as elements, and the books they've written as child element for each author.

I have all this information in the pubs database. First, I use a relational T-SQL query that shows me the information I'm after:

SELECT 
  a.au_fname
  , a.au_lname
  , c.type
  , c.title
FROM authors a
INNER JOIN titleauthor b
  ON a.au_id = b.au_id
INNER JOIN titles c
  ON b.title_id = c.title_id
ORDER BY a.au_lname, a.au_fname, c.type

Which produces this partial output:

au_fname    au_lname         type   title                   
-------------------- ---------------------------------------- ------------ -------------------------------------------------------------------------------- 
Abraham    Bennet         business  The Busy Executive's Database Guide
Reginald    Blotchet-Halls       trad_cook Fifty Years in Buckingham Palace Kitchens
Cheryl    Carson         popular_comp But Is It User Friendly?
Michel    DeFrance         mod_cook  The Gourmet Microwave
Innes    del Castillo        mod_cook  Silicon Valley Gastronomic Treats
Ann     Dull          popular_comp Secrets of Silicon Valley

The relational aspects of this output are shown by the duplicate names that show up when an author writes more than one book. I can use various GROUP BY and GROUPING clauses to segment the results if I include aggregated numeric values, but a better approach is to use XML, which can lay out the data as a hierarchy.

To create the hierarchies, I use several tools. First, I use the FOR XML EXCPLICIT predicate to the SELECT statement. That predicate allows me to specify the elements and attributes by hand, rather than allowing SQL Server to do it for me.

I also use the T-SQL UNION operator. This operator takes two separate queries and joins the result. To do that, there has to be the same number of columns in both queries, so I need to pad some columns in each query with NULLs. This creates the layout.

The XML query also needs to know how to create the hierarchy, so an ORDER BY is also important. Without it, the entire hierarchy shows up at the end of the last element from the first query.

The query is a bit complex, with a lot of steps, but not really complicated. Like T-SQL itself, to understand it, all you have to do is break down the component parts of the statement.

Here's the query in its entirety. I'll explain the code in a moment:

SELECT 1 AS Tag 
  , NULL AS Parent
  , authors.au_id AS [Author!1!AuthorID]
  , au_fname + ' ' + au_lname AS [Author!1!AuthorName]
  , NULL AS [Title!2!Type]
  , NULL AS [Title!2!TitleName]
FROM authors

UNION ALL

SELECT 2 AS Tag 
  , 1 AS Parent
  , authors.au_id
  , NULL
  , titles.type
  , titles.title
FROM authors 
INNER JOIN titleauthor 
  ON authors.au_id = titleauthor.au_id
INNER JOIN titles 
  ON titles.title_id = titleauthor.title_id
 
ORDER BY au_id

FOR XML EXPLICIT

Here's a partial result:

<Author AuthorID="172-32-1176" AuthorName="Johnson White">
  <Title Type="psychology " TitleName="Prolonged Data Deprivation: Four Case Studies"/>
  <Title Type="business " TitleName="The Busy Executive's Database Guide"/>
  <Title Type="business " TitleName="You Can Combat Computer Stress!"/>
</Author>

<Author AuthorID="213-46-8915" AuthorName="Marjorie Green"/>
<Author AuthorID="238-95-7766" AuthorName="Cheryl Carson">
  <Title Type="popular_comp" TitleName="But Is It User Friendly?"/>
  <Title Type="trad_cook " TitleName="Sushi, Anyone?"/>
</Author>

<Author AuthorID="267-41-2394" AuthorName="Michael O&apos;Leary">
  <Title Type="business " TitleName="Cooking with Computers: Surreptitious Balance Sheets"/>
</Author>

<Author AuthorID="274-80-9391" AuthorName="Dean Straight">
  <Title Type="business " TitleName="Straight Talk About Computers"/>
</Author>

<Author AuthorID="341-22-1782" AuthorName="Meander Smith">
  <Title Type="business " TitleName="The Busy Executive&apos;s Database Guide"/>
</Author>

Let's dissect this query a bit to see how it works. The first line of the query provides a "tag" to refer to its elements:

SELECT 1 AS Tag

Since it is the root of the data, I select a NULL as the parent in the second line:

  , NULL AS Parent

Then I provide the author's id; later, I use it to connect the two queries:

  , authors.au_id AS [Author!1!AuthorID]

I put the first and last names together, and call this element Author, with an attribute of AuthorName. I provide the 1 tag to show the level of hierarchy where the data resides:

  , au_fname + ' ' + au_lname AS [Author!1!AuthorName]

Because the UNION operator requires the same number of columns in the SELECT statements that it combines, I need to pad out the next two columns (or elements). I put both pieces of data under a single element (Title) and give them an attribute name of Type and TitleName. I also reference them to come from the second level of the hierarchy:

  , NULL AS [Title!2!Type]
  , NULL AS [Title!2!TitleName]

And then close out the first SELECT:

FROM authors

Now, I UNION the second query:

UNION ALL

The second SELECT is given a tag of 2, and then refers to its parent (1):

SELECT 2 AS Tag 
  , 1 AS Parent

I'll get that ID again, this time to use as a JOIN condition for the tables I need to get the other elements:

  , authors.au_id

And I place the NULL to pad out the UNION:

  , NULL

The next data points don't follow the same format as the first SELECT. That's because I've already specified the element and attribute tags in the first part of the query. All that's left is to join the relational tables and to specify that all-important ORDER BY:

  , titles.type
  , titles.title
FROM authors 
INNER JOIN titleauthor 
  ON authors.au_id = titleauthor.au_id
INNER JOIN titles 
  ON titles.title_id = titleauthor.title_id
 
ORDER BY au_id

FOR XML EXPLICIT

Try running this query on your system in the pubs database. The output will be in a single string, but for readability, you can add returns and tabs as I have here.

Try leaving off the ORDER BY and see how the results lay out. You'll see that all the authors are listed, and then the titles pile on to the last one.

This document ends up in attribute normal form. But by adding the "element" directive in the first part of the query (as I explained in my last article), you can get it into element normal form.

Next week, I'll explain how to work with Internet Information Server and SQL Server XML output.

Online Resources

The Data Direct Web site has a good article on XQuery, which coincidentally explains hierarchies in XML. You can find that info here.

InformIT Tutorials and Sample Chapters

Nicholas Chase also covers XQuery here.

< Back Page 240 of 365 Next >

🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Privacy Notice

Overview

Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security

Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children

This site is not directed to children under the age of 13.

Marketing

Pearson may send or direct marketing communications to users, provided that

Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
Such marketing is consistent with applicable law and Pearson's legal obligations.
Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out

Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

As required by law.
With the consent of the individual (or their parent, if the individual is a minor)
In response to a subpoena, court order or legal process, to the extent permitted or required by law
To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
To investigate or address actual or suspected fraud or other illegal activities
To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links

This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020

Email Address