Home > Articles

chap16_0789724499

  • Print
  • + Share This

Modifying SQL Server 2000 Data With Updategrams

In the preceding sections, you learned how to retrieve data from SQL Server in XML format, and how to use XML data inside a Transact-SQL process.

The XML for SQL Server Web Release, which you can download from the Internet as explained earlier, provides the following extra features:

  • Insert, delete, and update actual rows in SQL Server using XML updategrams.

  • Import XML data into SQL Server using the XML Bulk Load component.

An updategram is a XML template that contains before and after images of the data.

Because an XML document is a hierarchical document, changes to the data can affect multiple tables. You can use the transaction capabilities of updategrams to consider specific changes as members of the same transaction, maintaining data consistency across those changes. Every transaction is identified by a sync element. Listing 16.26 contains a simple updategram that changes the contact name of a customer.

Listing 16.26—A Simple Updategram That Changes a Customer's Contact Name

<CustomerUpdate xmlns:updg="urn:schemas-microsoft-com:xml-updategram">
 <updg:sync>
   <updg:before>
     <Customers CustomerID="ALFKI">
       <ContactName>Maria Anders</ContactName>
     </Customers>
   </updg:before>
   <updg:after>
     <Customers CustomerID="ALFKI">
       <ContactName>Stephen Johns</ContactName>
     </Customers>
   </updg:after>
 </updg:sync>
</CustomerUpdate>

Use Notepad to create the example from Listing 16.26 and save it as CustomerUpdate.xml in the Templates directory you created earlier in this chapter, in the "Creating a SQL Server Virtual Directory for IIS" section.

To execute this updategram, open Internet Explorer and type the following URL:

http://localhost/sqlxml/templates/CustomerUpdate.xml

Tip

If you receive an error message, check the spelling in the XML file. Remember that XML tags are case-sensitive.

You can open a new connection to SQL Server from Query Analyzer and check that the change has been made to the customer 'ALFKI' as defined in the updategram.

Looking at the example from Listing 16.26, you can identify the following sections:

<CustomerUpdate xmlns:updg="urn:schemas-microsoft-com:xml-updategram">

This line, at the beginning of the file, defines this XML file as an XML Template containing an updategram.

 <updg:sync>
 ...
 </updg:sync>

These two tags define the boundaries of a single transaction.

   <updg:before>
   ...
   </updg:before>

These two tags define the before image of the data. Somehow, you can consider this section as the WHERE clause in an UPDATE statement, where you define which rows will be updated.

   <updg:after>
   ...
   </updg:after>

Finally, these two tags delimit the values to update. This section produces the same action as the SET clause in an UPDATE statement.

In this example, you used the default mapping, where the XML code shows the actual names for tables and columns, in this case to the Customers table, and the CustomerID and ContactName columns. In some cases, you might prefer to provide a schema file, such as CustomerSchema.xml, in which case you must change the <updg:sync> line, in the updategram file, to provide the mapping-schema attribute, as in the following line:

 <updg:sync mapping-schema="CustomerSchema.xml">

Note

If the schema was not stored in the same path as the updategram, you can provide its full path in the mapping-schema attribute.

You can summit an updategram from an Active Server Page (ASP), by using ADO 2.6, as in the example from Listing 16.27.

Listing 16.27—Using ADO 2.6 in VBScript to Execute an Updategram

<%@ LANGUAGE = VBScript %>
<% Option Explicit %>

<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" content="text/html" charset="UTF-8"/>
<TITLE>SQL-XML by Example - SQLXML.asp</TITLE>

<%
 ' THIS IS THE SERVER SIDE SCRIPTING
 ' this part won't be visible from the client side

 ' some constants to make the code more readable
 ' some of these constants are available in the adovbs.inc file

 const adUseClient = 3
 const adWriteChar = 0
 const adWriteLine = 1
 const adExecuteStream = 1024

 ' Create a ADO Connection object

 Dim adoConn
 Set adoConn = Server.CreateObject("ADODB.Connection")

 ' Define the connection string to connect to a valid SQL Server 2000 instance
 ' and the Northwind database. Specify client side processing,
 ' which in this case will be in the IIS server

 ' Note: if your default instance is SQL Server 7, this code will not work
 '       unless you installed XML support for SQL Server 7.0

 Dim sConn
 sConn = "Provider=sqloledb;"
 sConn = sConn & "Data Source=MSSQLFGG\S2K;"
 sConn = sConn & "Initial Catalog=Northwind;"
 sConn = sConn & "User ID=sa"
 adoConn.ConnectionString = sConn
 adoConn.CursorLocation = adUseClient

 ' Open the connection

 adoConn.Open

 ' Create an ADO Command object, to send the XML query
 ' and receive the XML results

 Dim adoCmd
 Set adoCmd = Server.CreateObject("ADODB.Command")
 Set adoCmd.ActiveConnection = adoConn

 ' Let's define the XML updategram
 ' as in Listing 16.26
 ' Note that you must change " into ' because VBScript
 ' uses "" to enclosed constants

 Dim sQuery
 sQuery = "<CustomerUpdate "
 sQuery = sQuery & "xmlns:updg='urn:schemas-microsoft-com:xml-updategram'>"
 sQuery = sQuery & "<updg:sync>"
 sQuery = sQuery & "<updg:before>"
 sQuery = sQuery & "<Customers CustomerID='ALFKI'>"
 sQuery = sQuery & "<ContactName>Maria Anders</ContactName>"
 sQuery = sQuery & "</Customers>"
 sQuery = sQuery & "</updg:before>"
 sQuery = sQuery & "<updg:after>"
 sQuery = sQuery & "<Customers CustomerID='ALFKI'>"
 sQuery = sQuery & "<ContactName>Stephen Johns</ContactName>"
 sQuery = sQuery & "</Customers>"
 sQuery = sQuery & "</updg:after>"
 sQuery = sQuery & "</updg:sync>"
 sQuery = sQuery & "</CustomerUpdate>"

 ' Create and open the Stream object

 Dim adoStreamQuery
 Set adoStreamQuery = Server.CreateObject("ADODB.Stream")
 adoStreamQuery.Open

 ' Write the XML query into the Stream object

 adoStreamQuery.WriteText sQuery, adWriteChar
 adoStreamQuery.Position = 0

 ' Select the Stream object as the Command to execute
 ' Note the GUID for the Dialect property,
 ' this GUID represents the MSSQLXML format

 adoCmd.CommandStream = adoStreamQuery

 ' Now we will select to send the output to the Response object
 ' which is a Stream object too

 adoCmd.Properties("Output Stream") = Response

 ' We can execute the command with the updategram

 Response.write "Executing Updategram... "
 adoCmd.Execute , , adExecuteStream
 Response.write "Updategram Executed"
%>

</HEAD>
<BODY>
 <H1>SQL-XML by Example</H1>
 <H3>Updategram Execution</H3>
 <UL id=log>
 </UL>
</BODY>
</HTML>

As you can see, the example in Listing 16.27 is basically the same as the example in Listing 16.17. The only differences are the updategram and the lack of client-side scripting, which in this case it is not required.

Inserting SQL Server 2000 Data With Updategrams

In the preceding section, you learned how to update SQL Server data using updategrams. You can insert data into SQL Server using updategrams as well, as long as they don't contain an <updg:after> section.

Listing 16.28 contains an updategram that inserts a new category into the Categories table.

Listing 16.28—Inserting a New Category Through Updategrams

<CategoryAdd xmlns:updg="urn:schemas-microsoft-com:xml-updategram">
 <updg:sync>
   <updg:before>
   </updg:before>
   <updg:after>
     <Categories>
       <CategoryName>New Category</CategoryName>
     </Categories>
   </updg:after>
 </updg:sync>
</CategoryAdd>

As you can see in Listing 16.28, the before image is empty, and when executing this updategram, a new category will be added, using "New Category" as name, and having all the other fields with their default values, or NULL.

The insertion operation can be more complex. Insert a new category and a new product in that category in the same transaction. The problem is that CategoryID is an identity column, and we need that new value to be used in the Products table. Listing 16.29 shows the updategram to perform this action.

Listing 16.29—Inserting a New Category and a New Product in the New Category Through Updategrams

<CategoryProductAdd xmlns:updg="urn:schemas-microsoft-com:xml-updategram">
 <updg:sync>
   <updg:before>
   </updg:before>
   <updg:after updg:returnid="ID">
     <Categories updg:at-identity="ID">
       <CategoryName>More Category</CategoryName>
     </Categories>
     <Products CategoryID="ID" ProductName="New Product" Discontinued="1" />
   </updg:after>
 </updg:sync>
</CategoryProductAdd>

The example in Listing 16.29 has some new attributes:

   <updg:after updg:returnid="ID">

This directive instructs to return the Identity value automatically generated by SQL Server.

     <Categories updg:at-identity="ID">

In this case you define a variable name, ID, for the identity column.

     <Products CategoryID="ID" ProductName="New Product" Discontinued="1" />

You add a new product, using the recently generated Identity value stored in the ID variable, as CategoryID.

If you executed the updategram file as a URL from Internet Explorer, you will receive the response shown in Listing 16.30

Listing 16.30—Response After Inserting a New Category and a New Product Through Updategrams

- <CategoryProductAdd xmlns:updg="urn:schemas-microsoft-com:xml-updategram">
- <returnid>
 <ID>11</ID>
 </returnid>
 </CategoryProductAdd>

The value of 11 is the new identity value used for the new category.

Deleting SQL Server 2000 Data With Updategrams

In the preceding section, you learned how to use updategrams without the before image to insert new rows in SQL Server. Following the same concept, to delete rows from SQL Server you can use updategrams without the after image.

Listing 16.31 shows the updategram to delete the products and categories inserted in Listings 16.27 and 16.28.

Listing 16.31—Deleting Categories and Products Through Updategrams

<DeleteCatProducts xmlns:updg="urn:schemas-microsoft-com:xml-updategram">
 <updg:sync>
   <updg:before>
     <Products ProductName="New Product" />
     <Categories CategoryName="More Category" />
     <Categories CategoryName="New Category" />
   </updg:before>
   <updg:after>
   </updg:after>
 </updg:sync>
</DeleteCatProducts>

CAUTION

Be careful with how you define the before image in the updategram. Remember that this is the WHERE clause of your DELETE statement.

  • + Share This
  • 🔖 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.

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