SQL Server Reference Guide

Mar 28, 2003

␡

⎙ Print

< Back Page 253 of 365 Next >

Programming Applications: RSS Feeds from SQL Server

The average person today has access to more information than at perhaps any time in history: print media, billboards, television, radio, and, of course, several methods that the modern computer provides. With this plethora of avenues for information, users struggle to find a way to limit the stream of data.

In the Business Intelligence software world, the "clicks" paradigm is sometimes used to determine the best methods of delivering information to busy professionals.

In this paradigm, five levels (or "clicks") indicate the way the user gets data:

Level	Delivery	Use
0	Often called "The data finds you." The information is pre-formatted and sent to an E-mail inbox, pager or other technology.	Broad dissemination of high-level information.
1	The information is stored as a static report on a portal, Intranet, or other dynamic location.	Recurring wide-audience detailed reports.
2	The information is stored as a dynamic report similar to the one-click method, but various parameters are configurable, such as date ranges or locations.	Recurring wide-audience detailed reports with parameters.
3	A "blank-slate" tool, such as a reporting system, allows users to create their own reports.	High-level decision makers with a good understanding of corporate data.

The 4^th "click" is reserved for the technical professionals who design the other four levels.

At the first level (0-click), E-mail has been the favorite delivery technology. Unfortunately, unsolicited E-mail and corporate chatter have rendered this method largely ineffective.

To deliver data that a user wants to see, the best method is to have them sign up for it. One technology that directly addresses this need is Really Simple Syndication, or RSS.

NOTE

For more information on RSS, see Tristan Louis' article at http://www.informit.com/articles/article.aspx?p=169476; additional article references are at the end of this tutorial).

The long and short of RSS is that it's an XML file with specific elements. One set of elements in the file contains the information you want to publish to the user. The user enters the location of the RSS file into an "aggregator" program, which looks a bit like an E-mail client. When the RSS file is polled by the aggregator, the program displays the items that changed. You can create a headline, a short description, and a URL for the aggregator. This information can be as varied as corporate news, inventory changes, server statuses, blogs, and more.

There are a few ways to create these RSS files, but a database is ideal for storing the information for the RSS elements. A program can update the database with the information, and SQL Server can create an RSS file from the data. Or, SQL Server can store the data, and another program can extract it to create the RSS file. In either case, the aggregator (or "RSS Reader") checks the file location periodically and compares it to a cache of the previously checked RSS file. The new items are displayed for the user to read.

Let's take a step-by-step look at the process to create a database table for an RSS feed, and then explore the ways that SQL Server or another program can create the RSS file from that table.

To begin, let's examine how an RSS file is structured. It's an XML file, so it uses a header, footer, and in between there are specific tags to enclose "elements." These elements are the data for the XML content. To mark the elements, tags names are enclosed with less-than and greater-than symbols <>. To show the completion of the data element, the end-tags are also enclosed the same way, but begin with a forward slash /. An "outer" element must enclose an "inner" element. A simple tag arrangement looks a bit like this:

<Element 1>
	<Element 2> Data Goes in Here </Element 2>
</Element 1>

A "well-formed" RSS file looks like this:

<?xml version="1.0" encoding="utf-8" ?>
<channel>
<title>SiteName</title>
<description> Site Description </description>
<link>http://www.website.com</link>

<item>
 <title>Sample Headline 1</title>
 <pubdate>07/16/2004</pubdate>
 <description>Item Description 1</description>
 <link>http://www.someurl.com</link>
</item>

<item>
 <title>Sample Headline 2</title>
 <pubdate>07/17/2004</pubdate>
 <description>Item Description 2</description>
 <link>http://www.someurl.com</link>
</item>

</channel>
The first section of the file:
<?xml version="1.0" encoding="utf-8" ?>

is the header portion that tags this file as XML. The main tag of:

<channel>

sets the XML file to be accepted as an RSS file. The elements that follow:

<title>SiteName</title>
<description> Site Description </description>
<link>http://www.website.com</link>

are slightly static. If the SQL Server database services only one feed, then this information can be hard-coded into the RSS file before or after it's accessed by the database extract. If not, the elements between <title> and </title> can be stored in a table, along with the description and link elements. A final line, </channel>, also needs to be added after the database extract to complete the opening tag.

The "meat" of the RSS file is stored in the <item> tags. Each of these tags is the equivalent of an individual E-mail. Four elements are stored here: title, pubdate, description, and link.

The <title> element is the text to be displayed in bold in the aggregator. The <pubdate> displays the published date in the "date" column of the aggregator. The <description> tag is the text that appears in the main window, and the <link> tag redirects the aggregator when the user clicks the description.

To store these elements, use the code below to create a table to hold the data:

CREATE TABLE RSSFeed 
	(
	ItemID int identity (1, 1) NOT NULL 
	, ItemName varchar (100) NULL
	, PublishDate smalldatetime NULL
	, ItemDesc varchar (500) NULL
	, ItemURL varchar(100) NULL
	)
GO

NOTE

You'll want to create this table in the proper database. Don't put it in "master"!

There are only four elements that are required, so this code creates just those fields, along with a key. In more practical use, the data might be spread over several tables that already exist. If that's the case, a view accomplishes the same thing as this table.

The code below fills this new table with some sample values:

INSERT INTO RSSFeed ( 
ItemName
, PublishDate 
, ItemDesc 
, ItemURL 
)
VALUES 
(
 'Sample Headline 1'
, getdate()-3
, 'Item Description 1'
, 'http://www.someurl.com'
)
INSERT INTO RSSFeed ( 
ItemName
, PublishDate 
, ItemDesc 
, ItemURL 
)
VALUES 
(
 'Sample Headline 2'
, getdate()-2
, 'Item Description 2',
'http://www.someurl.com'
)
GO

The beauty of storing the RSS data in a database is that any program can keep the published items up-to-date. That program can be completely unaware of the RSS creation process.

It's important to remember that an RSS database operation is always either an insert or delete situation. The elements are similar to E-mail messages; once an E-mail has arrived, the sender can't reach into your in-box and change it.

This makes sense, since the information in an RSS feed is usually time-sensitive. There's seldom a need to re-write a simple message; normally, you just send an update.

For that reason, the SELECT statement used to extract the RSS message commonly uses a date range as a filter. Another alternative is to code the publishing application to remove older entries from the file.

The important part of that decision is to consider the data's timeliness. If the data is "stale" within a week, that would be the extract range. If users might not see the data for a month or more, the RSS file should include that range.

There are three choices for extracting element data for the RSS file. The first choice is to have an external program access the database and create the file from the elements provided.

Another option is to use T-SQL to create the entire file. By setting NOCOUNT ON, and removing the headers from the output, the SQL Statement below will create a complete RSS file as an output:

SET NOCOUNT ON
SELECT 
'<?xml version="1.0" encoding="utf-8" ?>' + CHAR(13)
, '<rss version="2.0">' + CHAR(13)
,'<channel>' + CHAR(13)
,'<title>SiteName</title>' + CHAR(13)
,'<description> Site Description </description>' + CHAR(13)
,'<link>http://www.website.com</link>' + CHAR(13)
SELECT
'<item>' + CHAR(13)
, '<title>', LTRIM(RTRIM(ItemName)) AS title, '</title>' + CHAR(13)
, '<date>', CONVERT(VARCHAR(10),PublishDate,101) AS pubdate, '</date>' + CHAR(13)
, '<description>' + LTRIM(RTRIM(ItemDesc)) AS description, '</description>' + CHAR(13)
, '<link>', LTRIM(RTRIM(ItemURL)) AS link, '</link>' + CHAR(13)
,'</item>', CHAR(13)
FROM 
RSSFeed 
SELECT
'</channel>' + CHAR(13)
,'</rss>'

The osql program or some other client can create the file on a regular basis using this select statement. Note that the code shown above does not specify a date range.

Another method is to combine the Web Assistant Wizard with SQL Server's XML features and the following query:

SELECT 
/*	
These items need to be in a format or header file:
<?xml version="1.0" encoding="utf-8" ?>
<rss version="2.0">
<channel>
<title>SiteName</title>
<description> Site Description </description>
<link>http://www.website.com</link>
*/
	 LTRIM(RTRIM(ItemName)) AS title
	, CONVERT(VARCHAR(10),PublishDate,101) AS pubdate
	, LTRIM(RTRIM(ItemDesc)) AS description 
	, LTRIM(RTRIM(ItemURL)) AS link
/*

And this needs to be at the end of the format or footer file:

</channel> 
</rss>
*/
FROM 
	RSSFeed item
FOR XML AUTO, ELEMENTS

A format file is required with this method, containing the header and footer elements in the comments. You can explore basic information about SQL's XML features in my article, "XML Overview".

There are several other articles at InformIT dealing with RSS aggregators and other applications. Make sure you check them out.

Online Resources

Everything you ever wanted to know about RSS origins and flavors is on the definitive resource for XML dialects – XML.com.

BlogSpace has a rundown on various RSS aggregators (readers) for various operating systems here.

InformIT Tutorials and Sample Chapters

Kevin Meltzer and Brent Michalski show you more about RSS, and also give examples of other tags.

Tristan Louis dives into RSS a little further in this article.

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