SQL Server Reference Guide

Mar 28, 2003

␡

⎙ Print

< Back Page 242 of 365 Next >

Security is an important part of any computing application. There is a never-ending balancing act between allowing valid users into an account while preventing invalid users from accessing the data.

This balancing act is further complicated when multiple interfaces exist for the data the application stores. SQL Server has many data entry points, and securing them all is a constant task.

One of these methods is Web services for SQL Server. Using this access method, you can allow direct T-SQL access into your system. When users have this kind of access, it's just like allowing them to install Query Analyzer on their desktops. Anything they can type and run there translates to the same access in the URL bar.

If you still want to allow access to the server using the HTPP protocol, but you'd like to enforce higher security, you can create T-SQL inside an XML file that the users run. They will receive the results of the query but won't see the query itself – nor will they be able to type a query in the URL address. This XML file is called a template.

In addition to the template, you can format the XML output into HTML or even text using a style sheet. The XML style sheet (XSL) is another XML document that specifies the format and placement of the data as elements and attributes. This is known as an XML Transform.

The final element in this process lives within the XSL document. The XSL document contains not only HTTP tags for formatting and placement, but also query elements to work with the data itself. The format for these queries is called XPath, a query language much like T-SQL. Learning the entire XPath syntax and structure is beyond the scope of this article, but I will show you enough elements of it to get you started. You can read more about the XPath specification in the links I provide in references section at the end of this article.

To summarize, the elements of this process are a template document which contains an SQL query, an XML document that it returns, a reference within the XML document to a style sheet (transform), and the style sheet that forms the end result. The SQL query creates a data set that XML uses, and the style sheet contains an XPath query that is able to trim or rearrange the data even further.

To begin, ensure that your server is ready for HTTP and SQL Server interaction. If you haven't set up your SQL Server and Web Server to work with XML, check out the last article in this series to see how to install the necessary prerequisites. The only difference in the process for using templates is that you do not need to check the boxes in the virtual site that allow URL queries.

Next, you need to create an XML file in the "template" directory of your SQL-enabled IIS virtual directory. Mine is located here:

C:\Inetpub\wwwroot\pubsdemo\template

The file contains three parts: a special namespace declaration, a tag representing a query, and the T-SQL for the query. I've explained tags before, and you know what a query is, but the concept of namespaces might be new to you.

A namespace is an XML attribute that serves two main purposes. The first purpose is that it provides a means of scope – meaning that a tag within one namespace is different than a similar tag in another namespace. The second purpose of namespaces is to provide instructions to an engine to treat the tags in a special way.

Here's a sample XML template from my system, called authors.xml:

<ROOT xmlns:sql="urn:schemas-microsoft-com:xml-sql">
<sql:query>
SELECT au_lname, au_fname
FROM authors
FOR XML AUTO
</sql:query>
</ROOT>

The outer element tag, marked ROOT, contains an attribute called xmlns. That starts a namespace, and what follows is the Microsoft-reserved keywords indicating a template query.

The element tag <sql:query> is recognized by the SQL-IIS layer (because of the namespace) and encloses the T-SQL that returns XML to the IIS engine. The tags are all closed out to create a well-formed XML document.

Entering http://localhost/pubsdemo/template/authors.xml in my browser returns this result:

- <ROOT xmlns:sql="urn:schemas-microsoft-com:xml-sql">
 <authors au_lname="Bennet" au_fname="Abraham" /> 
 <authors au_lname="Blotchet-Halls" au_fname="Reginald" /> 
 <authors au_lname="Carson" au_fname="Cheryl" /> 
 <authors au_lname="DeFrance" au_fname="Michel" /> 
 <authors au_lname="del Castillo" au_fname="Innes" /> 
 <authors au_lname="Dull" au_fname="Ann" /> 
 <authors au_lname="Green" au_fname="Marjorie" /> 
 <authors au_lname="Greene" au_fname="Morningstar" /> 
 <authors au_lname="Gringlesby" au_fname="Burt" /> 
 <authors au_lname="Hunter" au_fname="Sheryl" /> 
 <authors au_lname="Karsen" au_fname="Livia" /> 
 <authors au_lname="Locksley" au_fname="Charlene" /> 
 <authors au_lname="MacFeather" au_fname="Stearns" /> 
 <authors au_lname="McBadden" au_fname="Heather" /> 
 <authors au_lname="O'Leary" au_fname="Michael" /> 
 <authors au_lname="Panteley" au_fname="Sylvia" /> 
 <authors au_lname="Ringer" au_fname="Albert" /> 
 <authors au_lname="Ringer" au_fname="Anne" /> 
 <authors au_lname="Smith" au_fname="Meander" /> 
 <authors au_lname="Straight" au_fname="Dean" /> 
 <authors au_lname="Stringer" au_fname="Dirk" /> 
 <authors au_lname="White" au_fname="Johnson" /> 
 <authors au_lname="Yokomoto" au_fname="Akiko" /> 
</ROOT>

Although the template file contains the commands to process, the user receives only the result of the query, as shown here.

Now I take that return and use it within a style sheet. Before I do that, I need to make one change to the result. Since the file is rendered on the fly, I need to also add a directive to point to the style sheet I want. I change the authors.xml file to two new lines at the beginning:

<?xml version="1.0" ?>
<?xml-stylesheet type="text/xsl" href="authors.xsl"?>
<ROOT xmlns:sql="urn:schemas-microsoft-com:xml-sql">
<sql:query>
SELECT au_lname, au_fname
FROM authors
FOR XML AUTO
</sql:query>
</ROOT>

The xml-stylesheet directive in Line 2 points to a text file with the name authors.xsl in the same directory. This instructs the file to be processed using this style sheet, instead of the built-in style sheet most browsers carry.

The style sheet looks like this:

<?xml version="1.0" ?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<xsl:output method="html"/>
<xsl:template match="authors">
  <HTML>
    <table>
      <tr>
      <xsl:for-each select="*"/>
        <td><xsl:value-of select="@au_lname"/> , </td>
      <td><xsl:value-of select="@au_fname"/></td>
      </tr>
    </table>
  </HTML>
</xsl:template>
</xsl:stylesheet>

The second line of this file contains the namespace that the XML engine understands as style tag directives. Those directives make up the bulk of the tags in this file, but you'll see regular HTML tags mixed in.

The third line tells the browser to parse the return as HTML, as opposed to text or some other format.

The fourth line seeks a match for the node called authors. I can get away with that here, since there is only one node by that name, but if there was another further down on the tree, I'd need to qualify the placement by using the appropriate hierarchy names separated by forward slashes: authors/employs/authors. This is where part of the XPath navigation happens.

Next, I start the HTML tags, with an <HTML>, a <table>, and then a table row tag <tr>. Just below that I use a stylesheet namespace command called xsl:for-each, creating a loop, with an attribute called select. Within the parameters for that select, I use another XPath construct to ask for all members of the current node (the asterisk).

For each column within that row, I use yet another command called xsl:value-of with a select attribute of the attributes themselves – in this case, au_lname and au_fname. I specify that this is an attribute instead of an element by using an "at" sign in front of those names. I'd leave that sign out if those were the values of elements instead of attributes.

All that's left now is to close out all the tags. I save that file, call the original XML file in my browser, (http://localhost/pubsdemo/template/authors.xml) which refers to the stylesheet, which creates the HTML.

The output created by the stylesheet now has this format:

Bennet , Abraham 
Blotchet-Halls , Reginald 
Carson , Cheryl 
DeFrance , Michel 
del Castillo , Innes 
Dull , Ann 
Green , Marjorie 
Greene , Morningstar 
Gringlesby , Burt 
Hunter , Sheryl 
Karsen , Livia 
Locksley , Charlene 
MacFeather , Stearns 
McBadden , Heather 
O'Leary , Michael 
Panteley , Sylvia 
Ringer , Albert 
Ringer , Anne 
Smith , Meander 
Straight , Dean 
Stringer , Dirk 
White , Johnson 
Yokomoto , Akiko

There is an entire series of articles you should now read on stylesheets and XPath. Make sure you check the references.

Online Resources

One of the best tutorials on XPath that I've run across can be found here.

InformIT Tutorials and Sample Chapters

Nicholas Chase has a tutorial of XML stylesheets here. He also explains XPath.

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