SQL Server Reference Guide

Mar 28, 2003

␡

⎙ Print

< Back Page 237 of 365 Next >

My grandpa used to say, "Life is short. Eat dessert first." I'll take that let's-do-the-easy-stuff-first approach in this week's installment of my XML series on SQL Server Input and Output.

It's fairly simple to get XML data output from a query in SQL Server. In fact, every major database vendor now supports XML output of some sort. The hard part is inserting XML data into a database from an XML document. So lets eat desert first; we'll cover inserts in next week's article.

You can make any database that supports ANSI SQL create XML documents. Here's a simple script that would create an XML document from the pubs database in SQL Server:

/* 
Name: ANSIXML.sql
Purpose: Manually creates an XML file from selected
database fields. To be used on disparate
database platforms that do not have an XML
engine. Note that you have to code your own element tags.
Author: Buck Woody
Last 
Edited: 04/02/01
*/

SET NOCOUNT ON 
SELECT 
'<?xml version ="1.0" encoding = "UTF-8"?>' +CHAR(13)+
'<authors>'
GO
SELECT
'  <author id = "' + au_id+'">'+CHAR(13)+
'   <FirstName>'+au_fname+'</FirstName>'+CHAR(13)+
'   <LastName>'+au_lname+'</LastName>'+CHAR(13)+
'  </author>'+CHAR(13)
FROM authors

SELECT 
'</authors>'+CHAR(13)

This script isn't completely correct, as some XML parsing engines will bark at the xml directive tag at the top of the output. The proper way to render the line is actually:

<?xml version ='1.0' encoding = 'UTF-8'?>

You might want to escape out the double quotes with whatever the syntax of your platform requires if you use this method. You might also run into trouble with the CHAR(13) part I have here, so use whatever your platform needs to create a line feed. To be technical about it, you don't even need the linefeeds anyway; the whitespace is ignored.

You'll notice that I formatted this output in a very "element-centric" fashion. That means that the columns are broken out as an element for each heading. That's my preference in this situation; someone else might require something different. In XML, elements can repeat, and attributes can't. For instance, this is legal:

<FirstName>Buck</FirstName>
<FirstName>John</FirstName>
<FirstName>Jane</FirstName>

But this isn't:

<PAuthor FirstName="Buck" FirstName ="John" FirstName ="Jane">Woody</Author>

In this case, I reserved attributes as meta-data, and elements as column headings. It's completely acceptable to make the same output as attribute-centric instead, creating an element that essentially contains a row of data, like this:

<Author id="123-45-6789" FirstName="Buck" LastName="Woody"/>

The advantage of this approach is that the document is smaller, and the XML parsing engine doesn't have to move down a tree level (called a "node"), keeping track of where it is in the structure. Attributes can also be in any order, and don't need to be "nested" like elements are. Again, the situation will dictate your design choices.

Let's get back to the process for creating the XML. Why did Microsoft bother creating an engine in SQL Server to handle XML creation, if you can just hard-code some strings to do the same thing? For one thing, hard-coding requires touching the code each time the database structure changes. Microsoft includes a few ways to get data out of a database into an XML schema. You can select data with an extension to T-SQL, or use a Web interface to talk with SQL Server to create the documents.

Most T-SQL Statements can create an XML document with a simple modifier, called FOR XML. Here's a simple script to get the same type of XML out of the pubs database:

/* Simple XML output, 
attribute-centric
*/
SELECT 
au_id
, au_fname
, au_lname
FROM authors
FOR XML AUTO

Here's an abbreviated output from that statement:

<authors au_id="409-56-7008" au_fname="Abraham" au_lname="Bennet"/>
<authors au_id="648-92-1872" au_fname="Reginald" au_lname="Blotchet-Halls"/>
<authors au_id="238-95-7766" au_fname="Cheryl" au_lname="Carson"/>
<authors au_id="722-51-5454" au_fname="Michel" au_lname="DeFrance"/>
<authors au_id="712-45-1867" au_fname="Innes" au_lname="del Castillo"/>
<authors au_id="427-17-2319" au_fname="Ann" au_lname="Dull"/>
<authors au_id="213-46-8915" au_fname="Marjorie" au_lname="Green"/>

You might notice a couple of things right away about this output. First, it seems to violate the syntax rules I mentioned in the last two articles, since there are no beginning and closing tags. There's just one tag, and it's terminated at the end. That's actually OK for "empty" elements, that is, elements with no data in them.

Also, the output is not element-centric but attribute-centric. The tag repeats over and over, with the attributes completely inside in each tag. The qualifier on the query that created the XML is FOR XML AUTO. (There are other qualifiers to create the data as well, such as FOR XML RAW, which creates a "row" tag, and FOR XML EXPLICIT, which allows you to specify the "shape" of the XML data. We look at those two qualifiers later.)

The FOR XML AUTO qualifier has options to help us specify the XML output even further. The order of the SELECT statement creates the nesting of the XML document. This nesting refers to which element (or node) is the "parent" and which are the "children."

If what we're after is element-centric output, the FOR XML AUTO qualifier has an option to do that:

/* Simple XML output, 
attribute-centric
*/
SELECT 
au_id
, au_fname
, au_lname
FROM authors
FOR XML AUTO, ELEMENTS

And here's a partial output from that command:

<authors>
  <au_id>409-56-7008</au_id>
  <au_fname>Abraham</au_fname>
  <au_lname>Bennet</au_lname>
</authors>

The , ELEMENTS option is what does the trick.

As I mentioned, you can use most any T-SQL query to create the XML document, but there are some pretty serious limitations. For one, you can't use any aggregate functions in the query when you use FOR XML. This makes sense, because it's difficult to think of a result set like that as a tree. And that's the crux – it's important to keep in mind all the time that what you're really doing is mapping relational data to a hierarchical structure. Keep that concept in mind when you build your queries.

Another limitation is that you can't use a GROUP BY clause in the SELECT. You also can't use them in a subselect (which only makes sense), in a cursor, or in a view. You can use a view to select from. In other words, this won't work:

CREATE VIEW MyTestXMLView
AS 
SELECT * 
FROM pubs 
FOR XML AUTO

But this will:

SELECT * 
FROM SomeOtherView
FOR XML AUTO

We'll continue our XML journey next week.

Online Resources

Ronald Bourret has a fantastic treatise on XML and databases. First class!

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