SQL Server Reference Guide

Mar 28, 2003

␡

⎙ Print

< Back Page 239 of 365 Next >

I'm pretty impressed with things that are extensible. I like Swiss Army knives, I like multiple-use tools, and I like basic things that connect to other basic things to make new things.

I explained how to use the FOR XML select predicate in a previous article. I mentioned that there are a few limitations with the qualifier AUTO at the end of that predicate. In this week's article, I explore a couple of those weaknesses and show you a more powerful (if not more verbose) qualifier.

As you recall, the FOR XML AUTO predicate creates an XML output by turning a rowset based data set into a hierarchy. It does that by using the order of the SELECT statement and the column names to create the element or attribute names. One limitation with this predicate is that it is difficult to specify the element or attribute names directly. Another limitation is that it is difficult to make multiple levels in the XML document, and depending on the join, difficult to place these levels "after the fact." That basically means that to get the proper hierarchy, you have to keep the columns in order.

The answer to these issues is the FOR XML EXPLICIT predicate. It's longer to type, and takes a bit longer to understand, but once you do you'll find yourself using this statement as your primary way to get XML data into the format you want.

I've been using the authors table in the pubs database quite a bit throughout this series, but I use the titles table here to demonstrate a hierarchy. The titles table shows the names of books in the database. I also include the sales table, which shows the sales of each book. I stop at two levels of the hierarchy so that you have a chance to understand the concept, but you can apply it to as many levels as you need.

One of the best ways to explain this predicate is to define what I'm looking to accomplish, show the statement, and then break each component of the statement down with an example.

In this example, I'm looking for an attribute-normal form representation of the identifiers and titles of the books in the database. I need to create some T-SQL scripts that run daily to parse these out to a file location that another firm uses in their sales forecast application.

Now for the statement. I use a simple SELECT statement to retrieve the data, and then use the FOR XML EXPLICIT predicate to format it properly. The statement takes the following format:

SELECT column AS [Element Name!Tag Number!Attribute Name!Directive]
FROM
Table

That's the simplest form. In a moment, I'll ask for more columns than just one and also add a join condition, but let's keep it simple for now. The command is typed just as I have it here, with the [] and the ! marks. Here are the component parts of the SELECT statement:

Element Name: the name of the element that I place the column in.
Tag Number: shows the Level of the hierarchy, with 1 the highest.
Attribute Name: I want this in attribute-normal form, so the name of the attribute goes here. Even if I want to change that to element-normal form, the value still goes here.
Directives: Directives are optional commands that tell the processor to treat the data a little differently. They are:
cdata: This wraps the column in a CDATA element, which is similar to the <PRE> tag in HTML. It basically treats everything within it as plain text, and preserves indentation and so forth. If you use this directive, your font falls back to the default text font in your display.
element: Shows the data in element normal form.
hide: Hides the column.
ID, IDREF, and IDREFS: Define the keys and referencing attributes when using XMLDATA. I'll explain more about this concept in a future article.
Parent: The tag under which this element shows up.

Putting this into practical use, we have:

USE pubs
GO

SELECT 1 AS Tag 
  , NULL AS Parent
  , title_id AS [Book!1!ID]
  , title AS [Book!1!Title]
  , type AS [Book!1!Type]
FROM titles
FOR XML EXPLICIT

I selected a NULL value to hold the place of the parent node, since this is the root of the XML document. Here is a partial result of that query:

<Book ID="MC2222" Title="Silicon Valley Gastronomic Treats" Type="mod_cook "/>
<Book ID="MC3021" Title="The Gourmet Microwave" Type="mod_cook "/>
<Book ID="MC3026" Title="The Psychology of Computer Cooking" Type="UNDECIDED "/>
<Book ID="PC1035" Title="But Is It User Friendly?" Type="popular_comp"/>
<Book ID="PC8888" Title="Secrets of Silicon Valley" Type="popular_comp"/>
<Book ID="PC9999" Title="Net Etiquette" Type="popular_comp"/>
<Book ID="PS1372" Title="Computer Phobic AND Non-Phobic Individuals: Behavior Variations" Type="psychology "/>
<Book ID="PS2091" Title="Is Anger the Enemy?" Type="psychology "/>
<Book ID="PS2106" Title="Life Without Fear" Type="psychology "/>

As I mentioned in previous articles, in many cases I reserve attributes for meta-data. Assuming that I'll use the "type" tag of the book as meta-data, I rearrange the column order and modify two lines of the SELECT statement to include a directive to make certain fields return as elements:

SELECT 1 AS Tag 
  , NULL AS Parent
  , type AS [Book!1!Type]
  , title_id AS [Book!1!ID!element]
  , title AS [Book!1!Title!element]
FROM titles
FOR XML EXPLICIT

And here's a partial result of that query:

<Book Type="business ">
 <ID>BU1032</ID>
 <Title>The Busy Executive's Database Guide</Title>
</Book>

<Book Type="business ">
 <ID>BU1111</ID>
 <Title>Cooking with Computers: Surreptitious Balance Sheets</Title>
</Book>

<Book Type="business ">
 <ID>BU2075</ID>
 <Title>You Can Combat Computer Stress!</Title>
</Book>

Using FOR XML AUTO certainly simplifies the syntax of a SELECT, but doesn't offer this kind of flexibility. Using FOR XML EXPLICIT does require a bit more thought, and it allows you to create just the right document layout for your situation.

Next week, we'll continue this thread. I'll show you how to create hierarchies with the FOR XML EXPLICIT predicate.

Online Resources

If you've got a little time, Ronald Bourret has one of the best breakdowns of using XML as a database that I've seen. Check it out here: http://www.rpbourret.com/xml/XMLAndDatabases.htm#intro

InformIT Tutorials and Sample Chapters

Nicholas Chase covers SQL Server's XML capabilities as well. You can read his article here: http://www.informit.com/guides/content.aspx?g=xml&seqNum=115

< Back Page 239 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