SQL Server Reference Guide

Mar 28, 2003

␡

⎙ Print

< Back Page 238 of 365 Next >

In my last installment, I showed you how to create an XML document from SQL Server. Creating these documents isn't a difficult process; you just need to understand the syntax of the FOR XML predicate on a SELECT statement and how you want the document structured.

Using SQL Server to read a document, and potentially save data from it, is another story. You need to take a few steps to get the data in, process it, and navigate to find what you want.

This does make some sense. After all, SQL Server is a relational database management system, using set-theory concepts to join normalized groups of data together. XML is a markup standard designed primarily to represent hierarchical, de-normalized data. The ability to work with these two types of data at one time is no small task.

Here's one possible layout for a data structure in XML, in what's called an "element normal form" view:

<database>
 <table>
  <row>
  <column1>...</column1>
  <column2>...</column2>
  </row>
 </table>
</database>

The elements represent each distinct part of database objects. Another layout for representing data in XML is the "attribute normal form" view:

<database>
 <table>
  <row column1="Value" column2="Value"/>
 </table>
</database>

I make this distinction here because you need to keep the structure of the data in mind as you "shred" (or decompose) the data from a hierarchical form into a relational one. I mentioned in the last article that many people prefer the attribute-centric model because it requires one less navigation step – called "traversing a node."

Once you've got the structure defined, you can begin the process of importing data. There are two ways to import XML data. The first is to use a command called OPENXML, and the second is to use a program stream called XML Bulk Import. The second way is a bit involved for our needs here, so I'll cover it in another article.

There are four steps to use the OPENXML statement:

Open the XML Document
Prepare the data in memory
Query the data and map it
Close the document in memory

First, I need to get an XML document into memory. I do that by creating a variable to hold the document:

DECLARE @strXML varchar(4096)

I also set a variable to act as a "handle," or pointer. This allows SQL Server to get at the document's memory location.

DECLARE @idoc int

Now I need some XML data to work with. For this example, I'll just create some by hand, but normally I would read a document from a file location. I'll show you how to do that in a moment. Here's a simple XML snippet of a single book with three authors:

SET @strXML = 
'<Book>
<Author au_id="1234" au_fname="Buck" au_lname="Woody"/>
<Author au_id="1235" au_fname="Jon" au_lname="Glandon"/>
<Author au_id="1236" au_fname="Yvonne" au_lname="Madson"/>
</Book>'

This example is in attribute normal form. Next, I prepare the XML document for use with a special stored procedure:

EXEC sp_xml_preparedocument @idoc OUTPUT, @strXML

This requires a bit of explanation. The sp_xml_preparedocument "shreds" the XML hierarchy into a rowset-style data representation.

There are three arguments for this stored procedure. The first (@idoc) sets the memory handle location I mentioned a moment ago, the second (OUTPUT) directs the stored procedure to feed the shredded data to that memory location, and the third (@strXML) is the XML data.

Now I can use the XML document with the OPENXML command. It takes the following format:

SELECT au_fname, au_lname
FROM OPENXML(@idoc, '/Book/Author')
WITH (au_fname varchar(30)
  ,au_lname varchar(30)
  )

This is a standard SELECT statement, but the FROM predicate is parsed through the OPENXML function.

The OPENXML function shows two parameters in this example: the handle of the document in memory (@idoc) and the path to the node in which I'm interested. In this case, I navigated to the Book "root" node, then on to the node for Author. (I'll explain the path options in more detail in a future article.)

So far, I shredded the XML, asked for two attributes as fields, and told SQL Server where in the tree the data can be located. What's left is to map that data into data types that SQL Server understands. In the WITH predicate I define the two fields as varchar(30) types. I have to do that each time I get the data; But, if there is a table with the same field names that I've asked for with proper types in place, I can use that instead. Modifying the previous query to use the pubs database, I can use the authors table:

USE pubs
GO
DECLARE @strXML varchar(4096)
DECLARE @idoc int
SET @strXML = 
'<Book>
<Author au_id="1234" au_fname="Buck" au_lname="Woody"/>
<Author au_id="1235" au_fname="Jon" au_lname="Glandon"/>
<Author au_id="1236" au_fname="Yvonne" au_lname="Madson"/>
</Book>'
EXEC sp_xml_preparedocument @idoc OUTPUT, @strXML
SELECT au_fname, au_lname
FROM OPENXML(@idoc, '/Book/Author')
WITH 
  authors

Once I work with the data, I need to close the document.

EXEC sp_xml_removedocument @idoc

If I don't, the memory is left in use – and that's a problem. SQL Server restricts the amount of memory for the XML operations to one-eighth the total amount of memory for SQL Server. That means that you should use this command for passing data in small chunks.

Of course, you won't often create an XML document using Query Analyzer. You have two options to bring the document into the variable. You can send the data along with a Visual C# or other programming language, or you can use the xp_cmdshell stored procedure to type a document and then store the result in the variable. Here's an example of that:

CREATE TABLE #xmltable (string VARCHAR(4000))
INSERT #xmltable EXEC master..xp_cmdshell 'type c:\temp\test.xml'
SELECT string 
FROM #xmltable
DROP TABLE #xmltable

Here's the complete code, not including the file read:

DECLARE @strXML varchar(4096)
DECLARE @idoc int
SET @strXML = 
'<Book>
<Author au_id="1234" au_fname="Buck" au_lname="Woody"/>
<Author au_id="1235" au_fname="Jon" au_lname="Glandon"/>
<Author au_id="1236" au_fname="Yvonne" au_lname="Madson"/>
</Book>'
EXEC sp_xml_preparedocument @idoc OUTPUT, @strXML
SELECT au_fname, au_lname
FROM OPENXML(@idoc, '/Book/Author')
WITH (au_fname varchar(30)
  ,au_lname varchar(30)
  )
EXEC sp_xml_removedocument @idoc

There's a great deal more to this topic that we'll cover in the next few articles. I'll explain how to use structures to navigate the data more easily. I'll also show you how to read more than a small amount of XML data into SQL Server.

Online Resources

Michael Rys is the product Manager for SQL Server XML. SQL Summit has published an interview with him that makes for a good read. You can find it here: http://www.sqlsummit.com/People/MRys.htm

InformIT Tutorials and Sample Chapters

Nicholas Chase explains XML in databases in his article called "XML and Databases." You can read it here: http://www.informit.com/guides/content.aspx?g=xml&seqNum=110

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