SQL and Xquery Tutorial For Ibm Db2, Part 1

SQL and XQuery tutorial for IBM DB2, Part 1:
Introduction to Aroma and SQL

Skill Level: Introductory
Pat Moffatt (pmoffatt@ca.ibm.com)

Information Management Program Manager, IBM Academic Initiative
IBM
Bruce Creighton (bcreight@ca.ibm.com)

Skills Segment Planner
IBM
Jessica Cao
Training Tools Developer
IBM
03 Aug 2006
This tutorial introduces readers to the Aroma database to apply Structured Query
Language (SQL) and XML Query (XQuery) knowledge to solve typical business
questions. Also included are detailed instructions for installing DB2® and the Aroma
database. This tutorial is Part 1 of the SQL & XQuery tutorial for IBM DB2 series.
Section 1. Before you start
About this series

This tutorial series teaches basic to advanced SQL and basic XQuery topics and
shows how to express commonly asked business questions as database queries by
using SQL queries or XQueries. Developers and database administrators can use
this tutorial to enhance their database query skills. Academic Initiative members can
use this tutorial series as a part of their database curriculum.
Introduction to Aroma and SQL Trademarks

© Copyright IBM Corporation 2006. All rights reserved. Page 1 of 26
developerWorks® ibm.com/developerWorks
All the examples in this document are based on Aroma, a sample database that
contains sales data for coffee and tea products sold in stores across the United
States. Each example consists of three parts:
• A business question, expressed in everyday language

• One or more example queries, expressed in SQL or XQuery
• A table of results returned from the database
This guide is designed to allow participants to learn the SQL language and XQuery.
As with any learning, it is important to supplement it with hands-on exercises. This is
facilitated by the table definitions and data.
For students using this as part of an academic class, obtain from your instructor the
instructions to connect to the Aroma database and learn about any differences
between the guide and your local set up.
This tutorial was written for DB2 Express-C 9 for UNIX®, Linux® and Windows®
(formerly known as Viper).
About this tutorial

This tutorial introduces participants to the Aroma database, especially the retail
group of tables, table definitions, sample data, and the relationship between tables.
These tables were created to show an environment where:
• There are few tables

• Column names use the analyst's vocabulary
• Columns are reflective of the natural dimension of the business
This is a typical, small data warehouse using a star schema. The other type of
database is Online Transaction Processing (OLTP). OLTP databases contain
transacations at the most granular level.
This tutorial also introduces the basics of SQL and suggests some typical business
questions that IBM DB2 9 can be used to answer.
System requirements
To use this tutorial to the fullest, you should have IBM DB2 9 installed. Download
DB2 Express-C, a no-charge version of DB2 Express Edition for the community that

ibm.com/developerWorks developerWorks®
offers the same core data features as DB2 Express Edtion and provides a solid base
to build and deploy applications. You will also need to install the Aroma database,
which can be downloaded from here.
Installing DB2 Express-C 9

To install DB2 9, follow these steps (default options should be used unless otherwise
specified):
1. Navigate to the folder containing the downloaded file -

db2exc_viper_WIN_x86.zip (we will assume the file is downloaded to the
C:\DownloadDirector folder).
2. Unzip the file.
3. Find setup.exe in the unzipped folder and double-click on it. The DB2
Setup Launchpad will appear.
4. Within the DB2 Setup Launchpad, click on Install a Product from the
panel on the left.
5. Click on Install New under DB2 Express.
6. In the installer, click Next to view the License Agreement. You will need to
Accept the agreement to continue and click Next.
7. Choose a Typical installation and click Next.
8. Confirm that you plan to "Install DB2 Universal Database Express Edition
on this computer and save my settings in a response file" and click Next.
9. Verify the installation directory and click Next.
10. In the "Configure DB2 instances" screen, click Next.
11. In the "User Information" screen, set the Domain to None -- use local
user account using the pull-down menu, use db2admin as the User
name, and set a password.
(Optionally, you can select the LocalSystem account, but there are
limitations introduced if this option is used. Click the Help button to learn
more.)
12. Make sure the checkbox Use the same user name and password for
the remaining DB2 services is checked and click Next.

13. Click Next to skip the "Prepare the DB2 tools catalog" screen.
14. To simplify installation, uncheck Set up your DB2 server to send

notifications and click Next.
15. Verify that the Enable operating system security checkbox is checked.
Leave the DB2 administrators group as the default value DB2ADMNS and
leave DB2 users group as the default value DB2USERS. Click Next.
16. Click Finish to start the DB2 product installation when you reach the
"Start copying files and create response file" screen.
17. When the installation is complete, a window with the message "Setup is
complete" will appear. Click Finish to complete the installation procedure.
18. A window entitled "DB2 First Steps" will now appear. Click Create profile.
Your Web browser will open a page called DB2 First Steps. This tutorial
contains many useful links to information on DB2, but it will not be used
during this tutorial. Close your Web browser and continue with this
tutorial.
Installing the Aroma database
1. Ensure DB2 Express-C 9 is installed.
2. Start the Command Window from the Start menu ==> all Programs ==>
IBM DB2 ==> Command Line Tools ==> Command Window.
3. Execute create_aroma.bat in the Command Window.

Note: Don't forget to move to the directory where the batch file is located
using the cd command.
4. Two files, create.txt and report.txt, will be created. Edit report.txt and
compare to the expected results below:
TABLE RECORDS
--------------------- -----------
aroma.class 9
aroma.deal 9
aroma.line_items 182
aroma.market 17
aroma.orders 27
aroma.period 821
aroma.product 59
aroma.promotion 194

aroma.sales 69941
aroma.store 18
aroma.supplier 9
XML support
XML and basic XQueries will be introduced in Part 7 of this series. To support XML,
the aromadb database was created with the statement:
db2 create db aromadb using codeset utf-8 territory us
Note the specification of UTF-8 as the codeset for the database. The use of XML
features is restricted to a database that is defined with codeset UTF-8 and has only
one database partition. When creating your own databases in the future, don't forget
to include this parameter or your database won't support XML features!
Section 2. Aroma database group of tables

Most of the examples in this guide are based on data from the Aroma database,
which tracks aggregated daily retail sales in stores owned by the Aroma Coffee and
Tea Company. The Aroma database contains tables that are used to understand the
sales for the Aroma Coffee and Tea Company. There are six tables, which are used
to create different groupings and to understand the sales. The tables are: Sales,
which contain the sales transactions or facts; Period, Product, Store, Promotion
Class, and Market. These are referred to as the retail group of tables.
Another set of tables contain data to understand the purchases of Aroma Coffee and
Tea Company. This set of tables is referred to as the purchasing group of tables and
can be used to understand the purchases from suppliers. This group of tables is not
used in any examples in this tutorial. It only exists in the Appendix to provide a more
complete picture of the Aroma Coffee and Tea Company.
Figure 1. Retail group of tables

The crow's feet in this diagram indicate a one-to-many relationship between two
tables. For example, each distinct value in the Perkey column of the Period table
can occur only once in that table but many times in the Sales table. Column names
in bold are primary-key columns. Column names in italics are foreign-key columns.
Column names in bold italics are primary and foreign-key columns.
Sample data from each table is presented in the following sections so you can see
how these primary-key to foreign-key relationships work.
A primary key is a unique key that is a part of the definition of the table. A table
cannot have more than one primary key, and the columns of a primary key cannot
contain null values. (Null values will be discussed later in detail. If a value is null, that
means there is a place to store the data, but nothing is there - this is different from a
blank.) Primary keys are optional and can be defined in CREATE TABLE or ALTER
TABLE statements. Primary keys are important because there can only be one
occurrence of each value; the same row will always be selected. There may be a
couple of cities with the same name; however, selecting the record based on the
primary key will ensure the same row is always selected.
A foreign key is specified in the definition of a referential constraint. A table can have
zero or more foreign keys. The value of the composite foreign key is null if any
component of the value is null. Foreign keys are optional and can be defined in
CREATE TABLE statements or ALTER TABLE statements.

Section 3. Basic Aroma tables

The tables and columns are named with familiar business terms, making them easy
to understand and use. A well-designed set of tables provides the following benefits
to application developers and end users:
• Business questions are easy to express as SQL queries

• Queries run fast and return consistent answers.
You will notice that the Aroma database does not record each transaction that takes
place. The data has been aggregated to reflect the total sales at each store of a
given product on a given day under a particular promotion.
Aggregated data is typical of data warehouses. The idea is to summarize data so

there are not as many rows. Normally this is done by a database administrator
(DBA) or computer program, and is commonly referred to as ETL (Extract,
Transform, Load).
Period, Product, and Class dimensions

Period Table
The following table displays the first few rows of the Period table. The primary-key
column is the Perkey column:
Perkey Date Day Week Month Qtr Year

1 2004-01-01TH 1 JAN Q1_04 2004
2 2004-01-02FR 1 JAN Q1_04 2004
3 2004-01-03SA 1 JAN Q1_04 2004
4 2004-01-04SU 2 JAN Q1_04 2004
5 2004-01-05MO 2 JAN Q1_04 2004
6 2004-01-06TU 2 JAN Q1_04 2004
...
Product and Class Tables
The following table displays the first few rows of the Product table. The primary key
is a combination of the Classkey and Prodkey values:

Classkey Prodkey Prod_Name Pkg_Type

1 0 Veracruzano No pkg
1 1 Xalapa Lapa No pkg
1 10 Colombiano No pkg
1 11 Espresso XO No pkg
1 12 La Antigua No pkg
1 20 Lotta Latte No pkg
...
Note: recall that a primary key is a unique key that is a part of the definition of the
table. Normally, a primary key is a single column in a table. In this case, the primary
key is a combination of two columns, which means that there can only be one
combination like this in a table.
The following table displays the first few rows of the Class table.
Classkey Class_Type Class_Desc

1 Bulk_beans Bulk coffee products
2 Bulk_tea Bulk tea products
3 Bulk_spice Bulk spices
4 Pkg_coffee Individually packaged coffee
products
5 Pkg_tea Individually packaged tea
products
6 Pkg_spice Individually packaged spice
products
Store, Market, and Promotion tables

The Store, Market, and Promotion tables contain descriptions that data analysts use
as they query the database. For example, the Store table contains store names and
addresses; the Product table contains product and packaging information; and the
Period table contains month, quarter, and year values. Every table contains a
primary key that consists of one or more columns; each row in a table is uniquely
identified by its primary-key value or values.
Store and Market tables
The following table displays the first few rows of the Store table (some columns
were truncated to fit on the page). The primary-key column is Storekey; Mktkey is a

foreign-key reference to the Market table.
Storekey Mktkey Store_Type Store_NameStreet City State Zip

1 14 Small Roasters, 1234 Los Gatos CA 95032
Los Gatos University
Ave
2 14 Large San Jose 5678 San Jose CA 95156
Roasting Bascom
Ave
3 14 Medium Cupertino 987 Cupertino CA 97865
Coffee DeAnza
Blvd
4 3 Medium Moulin 898 Main New LA 70125
Rouge Street Orleans
5 10 Small Moon 98675 Detroit MI 48209
Pennies University
6 9 Small The Coffee 9865 Chicago IL 06060
Club Lakeshore
Bl
...
The following table displays the first few rows of the Market table.
Mktkey Hq_city Hq_state District Region

1 Atlanta GA Atlanta South
2 Miami FL Atlanta South
3 New Orleans LA New Orleans South
4 Houston TX New Orleans South
5 New York NY New York North
...
Promotion table
The following table displays the first few rows of the Promotion table. The
primary-key column is Promokey.
Promokey Promo_Type Promo_Desc Value Start_Date End_Date

0 1 No Promotion 0.00 9999-01-01 9999-01-31
1 100 Aroma catalog 1.00 2004-01-01 2004-01-31
coupon
2 100 Aroma catalog 1.00 2004-02-01 2004-02-29
coupon

3 100 Aroma catalog 1.00 2004-03-01 2004-03-31

coupon
4 100 Aroma catalog 1.00 2004-04-01 2004-04-30
coupon
5 100 Aroma catalog 1.00 2004-05-01 2004-05-31
coupon
...
The Value column identifies the cash value of a given promotion. The user can
evaluate the cost of the promotions by summing these values.
Sales table
The following table displays the first 20 rows of the Sales table.
Perkey Classkey Prodkey Storekey Promokey Quantity Dollars Comments

2 2 0 1 116 8 34.00 ...
2 4 12 1 116 9 60.75 ...
2 1 11 1 116 40 270.00 ...
2 2 30 1 116 16 34.00 ...
2 5 22 1 116 11 30.25 ...
2 1 30 1 116 30 187.50 ...
2 1 10 1 116 25 143.75 ...
2 4 10 2 0 12 87.00 ...
2 4 11 2 0 14 115.50 ...
2 4 22 2 0 18 58.50 ...
2 4 0 2 0 17 136.00 ...
2 5 0 2 0 13 74.75 ...
2 4 30 2 0 14 101.50 ...
2 2 10 2 0 18 63.00 ...
2 1 22 3 0 11 99.00 ...
2 6 46 3 0 6 36.00 ...
2 5 12 3 0 10 40.00 ...
2 1 11 3 0 36 279.00 ...
2 5 1 3 0 11 132.00 ...
2 5 10 3 0 12 48.00 ...
...

The primary-key definition is a combination of values from five columns:
perkey, classkey, prodkey, storekey, promokey
About the Sales table

The Sales table contains data that is easily accessible throughout the business
attributes defined in the table it references, and it stores large amounts of statistical
information about those attributes. The Sales table is the largest table in this
database.
The last column, Comments, stores information about customer feedback using the
XML data type. XML is introduced in Part 7 of this series.
Multipart primary key
The Sales table contains a multipart primary key. Each of the key's five columns is a
foreign-key reference to the primary key of another table:
perkey, classkey, prodkey, storekey, promokey
This primary key links the Sales data to the Period, Product, Store, and
Promotion tables.
Gold table
The Gold table contains information for "Gold Card" customers that allow them to
enjoy various discounts, free gifts, and e-mail reminders of promotional activities.
The Gold table will be created by the participant in Part 6 of this series, and will have
the following columns: unique card ID, store key, first name, last name, e-mail, and
status.
Section 4. What is SQL?
Structured Query Language

Structured Query Language (SQL) is a standardized language for defining and

manipulating data in a relational database. All relational database management

systems (RDBMS) understand SQL.
Here is some more information about SQL:
• SQL was devised specifically as part of the relational theory. You need a
language to talk to your database, to retrieve data from it, or to make
changes to the data.
• SQL is a non-navigational language. In other words, with SQL, you don't
have to tell DB2 to find a record, read its pointer, and follow that pointer to
a related row in the table. Simply tell DB2 what to do and DB2 figures out
how to handle the command. It's that simple!
• You can use SQL to modify aspects of a table without having to take the
table offline, add new columns to an existing table, or add business rules
to the definition of the table.
Commonly asked questions

Here is a sampling of business questions that you can use SQL to answer. With the
answers, critical business decisions can be made in a timely manner.
Easy
• What were the weekly sales of Lotta Latte brand coffee in San Jose
during last year?
• What were the average monthly sales of all coffee products in the West
during each month of last year?
Moderately difficult
• How do the sales of Lotta Latte in San Jose compare with its sales in Los
Angeles and New York?
• How has the monthly market share of Lotta Latte changed during the last
two years in all markets?
• Which suppliers charge the most for bulk tea products?
• What was the most successful promotion last December in California?
Very challenging business questions, which DB2 9 can be used to provide
answers.

• What were the running totals for Lotta Latte sales during each month of
last year?
• What were the ratios of monthly sales to total sales (expressed as
percentages) for Lotta Latte during the same period?
• Which ten cities had the worst coffee sales in 2004 with regard to dollar
sales and quantities sold?
• Which Aroma stores fall into the top 25 percent in terms of sales revenue
for the first quarter of 2005? Which stores fall into the middle 50 percent,
and which fall into the bottom 25 percent?
Section 5. Data types

Data types define acceptable values for constants, columns, host variables,
functions, expressions, and special registers. In the most introductory form, data
must be defined as either a numeric data type or a text data type. This is important
for two main reasons. First, with numeric data types, mathematical functions can be
applied, such as adding fields together or subtracting fields. Second, to ensure the
right type and amount of storage is allocated, the size can be preset. How many
times have you filled in an application and there was not enough space to write
everything required? However, increasing all fields to the maximum leads to too
much empty space in the database. This section describes the data types referred to
in the examples. For a full list and complete description of other data types, refer to
the SQL Reference Guide .
Numbers
All numbers have a sign and a precision. The precision is the number of bits or
digits, excluding the sign.
SMALLINT A SMALLINT (small integer) is a

two-byte integer with a precision of 5
digits.
INTEGER An INTEGER (large integer) is a
four-byte integer with a precision of 10
digits.
BIGINT A BIGINT (big integer) is an eight-byte
integer with a precision of 19 digits.
REAL A REAL (single-precision floating-point

number) is a 32-bit approximation of a

real number.
DOUBLE A DOUBLE (double-precision
floating-point number) is a 64-bit
approximation of a real number.
DOUBLE is also referred to as FLOAT.
DECIMAL(p,s) A DECIMAL is a decimal number. The
position of the decimal point is
determined by the precision (p) and the
scale (s) of the number. Precision is
the total number of digits and has to be
less than 32. Scale is the number of
digits in the fractional part and is
always smaller than or equal to the
value of precision. The decimal value
defaults to precision of 5 and scale of 0
if precision and scale are not specified.
Character string
A character string is a sequence of bytes. The length of the string is the number of
bytes in the sequence. If the length is zero, the value is called the empty string.
Fixed-Length Character String CHAR(x) is a fixed length string. The length

attribute x must be between 1 and 254, inclusive.
Varying-Length Character String Varying-length character strings are of three
types: VARCHAR, LONG VARCHAR, and CLOB.
VARCHAR(x) types are varying-length strings, so
a string of length 9 can be inserted into
VARCHAR(15) but will still have a string length of
9.
See Large Objects (LOBs) for details on CLOB.
Graphic string
A graphic string is a sequence of double-byte character data.
Fixed-Length Graphic String GRAPHIC(x) is a fixed length string. The length

attribute x must be between 1 and 127, inclusive.
Varying-Length Graphic String Varying-length graphic strings are of three types:
VARGRAPHIC, LONG VARGRAPHIC, and
DBCLOB. See Large Objects (LOBs) for details
on DBCLOB.

Binary string
A binary string is a sequence of bytes. It is used to hold nontraditional data, such as
pictures. Binary Large OBject (BLOB) is a binary string. See Large Objects (LOBs)
for more information.
Datetime values
Datetime values are representations of dates, times, and timestamps (a character
string of 14 digits that represents a valid date and time in the form
yyyyxxddhhmmss). Datetime values can be used in certain arithmetic and string
operations and are compatible with certain strings; however, they are neither strings
nor numbers.
Date A date is a three-part value (year, month, and

day).
Time A time is a three-part value (hour, minute, and
second) designating a time of day using a
24-hour clock.
Timestamp A timestamp is a seven-part value (year, month,
day, hour, minute, second, and microsecond)
designating a date and time.
Null value
The null value is a special value that is distinct from all non-null values. It means the
absence of any other value for that column in the row. The null value exists for all
data types.
XML
DB2 9 is the industry's first hybrid data server for managing data from both relational
and pureXML™ structures. DB2 9 has introduced an optimized data storage engine
for XML data alongside the existing relational engine.
XML is self-describing in that the meaning of the data is included in the record. The
Comments column uses the XML data type to store customer comments. See Part 7
of this series for more details.

Section 6. Ways to run SQL

To talk to DB2, you use a tool, specific to a platform, to enter your SQL. These tools
are included when you install the product. For the purpose of this series, use the
Control Center or the Command Line Processor (CLP).
The Control Center

SQL statements, DB2 commands, and operating-system commands can be run from
the Control Center. Open the Control Center from the Start menu ==> all Programs
==> IBM DB2 ==> General Administration Tools ==> Control Center. From the
menu at the top of the interface, select Tools ==> Command Editor. A command
editor window will pop up and allow you to enter SQL statements.
You can run these interactively or you can save your statements in a script. To
execute these statements, you would click the Play icon in the upper-left corner of
the graphic (circled in Figure 2, below).
Figure 2. Control Center
Command Line Processor

Statements can alternatively be run from the Command Line Processor (CLP). Open
the CLP from the Start menu ==> all Programs ==> IBM DB2 ==> Command Line
Tools ==> Command Line Processor.
Figure 3. Command Line Processor
Section 7. Getting started
Connecting to a database
You need to connect to a database before you can use SQL statements to query or
manipulate data. The CONNECT statement associates a database connection with
a user name.
To connect to the aromadb database, type the following command in the DB2
command line processor:
CONNECT TO aromadb USER userid USING password
If you are using this guide as part of a classroom, ask your instructor for the userid
and password to connect to the database.
If no userid and password are required, or if you are using this in a self-study mode

and using your own computer, simply type the following command:
CONNECT TO aromadb
The following message tells you that you have made a successful connection:
Database Connection Information

Database server
= DB2/NT 9.0.0
SQL authorization ID = USERID
Local database alias = AROMADB
Once you are connected, you can start using the database.
DB2 Information Center

In addition to the standard set of documentation available for DB2 9, there is also a
searchable online collection of DB2 information that simplifies the tasks associated
with DB2 9. The DB2 Information Center allows a user to receive help on any
number of issues.
The DB2 Information Center is accessible through a standard Web browser or

through built-in facilities in a number of the graphical user interfaces that come with
DB2 9. Currently Microsoft Explorer (version 5 and later) and Netscape Navigator
(version 6.1 and later) are supported.
Contents of the DB2 Information Center are updated with each product or fixpak
release. Be certain you know which version of DB2 you are running to ensure that
you obtain the correct information. The DB2 Information Center becomes more
helpful the more that you take advantage of it. As you become familiar with the
options available, you can narrow your search more effectively and get the answers
to your questions more efficiently.
• You can easily access the DB2 Information Center from the Start menu
==> all Programs ==> IBM DB2 ==> Information ==> Information
Center.
• Alternatively, you could use this url:
http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp
Example
In Part 3 of this series you will encounter an error when you attempt to execute a
query that incorporated mismatched datatypes. You will receive the following error

message:
[IBM][CLI Driver][DB2/LINUX] SQL0401N The data types of the operands

for the operation ">" are not compatible. SQLSTATE=42818
To better understand the meaning of this message, you may want to research the
details of the error and learn the corrective action you should take.
1. Navigate to the DB2 Information Center.
2. Enter the error code from the error message (SQL0401N) in the Search
box at the top left corner.
3. Click GO.
4. The result set displays two results. The first result is "100% SQL0401",
indicating that it is 100% relevant, while the second result is only 8%
relevant. Select the first one.
5. Read the results of the search.
Section 8. Metadata
Metadata can be defined as data about the structure of the database itself. This data
includes information such as lists of the tables, indexes, columns, and more included
in the database.
You will often hear metadata called by other names, including catalog data or
system tables. Metadata is automatically collected by DB2 9 whenever a user takes
an action to create, delete, or change some aspect of the database.
The standards of storing data established for conventional SQL do not apply to the
storage of metadata. Each database provider sets up unique methods to store and
process the metadata. Knowing how to retrieve this information can be of
tremendous assistance in working with a database.
Metadata, however, is considered by many database administrators to be somewhat

confidential in nature. As a result, many users will not have access to the collection
of metadata. You will have to learn at your individual location what your access to
metadata will be.

System tables
DB2 9 stores metadata in nearly 100 system tables. They are all contained in the
SYSIBM schema. This schema is created automatically each time a database is
created. System tables also follow a standard naming convention. Each table name
begins with SYS, as in SYSTABLES, SYSINDEXES, and SYSUSERAUTH. (For this
reason, user-defined tables cannot begin with the letters SYS.)
A user retrieves metadata from system tables in much the same way as data from
regular tables. SQL statements behave the same in both cases. Knowledge of the
structure of the tables is all that is needed. Given the appropriate authorizations, a
user can obtain a list of all of the system tables holding metadata by querying the
database.
Example query
SELECT name
FROM sysibm.systables
WHERE name LIKE 'SYS%';
Result
NAME
SYSATTRIBUTES
SYSBUFFERPOOLNODES
SYSBUFFERPOOLS
...
SYSTABLES
...
SYSXSROBJECTS
You may or may not be able to execute the above query, depending on permissions
you have been granted by the System Manager and/or Database Administrator.
If you execute the above query without the WHERE clause, you will obtain a list of
all tables in the database. The result set will be ordered by Creator (schema) and
alphabetically by table name within each Creator. The column name "Creator"
assumes that the schema identified for each table has the same name as its creator.

Example query
SELECT name, creator

FROM sysibm.systables;
Result
NAME CREATOR
CLASS AROMA
... AROMA
SUPPLIER AROMA
... ...
SYSATTRIBUTES SYSIBM
... SYSIBM
SYSXMLSTATS SYSIBM
... ...
By constraining on the name of the schema, you can limit the result set to those
tables that are part of a given schema.
Example query
SELECT name, creator

FROM sysibm.systables
WHERE creator='AROMA';
Result
NAME CREATOR
CLASS AROMA
... AROMA
SUPPLIER AROMA
Similarly, you can list information about the columns in a specific table by accessing
the sysibm.syscolumns system table.

Example query
SELECT * FROM sysibm.syscolumns WHERE tbname='CLASS' AND
tbcreator='AROMA';
Result
NAME TBNAME TBCREATOR REMARKS COLTYPE ...
CLASS_DESC CLASS AROMA CHAR ...
CLASS_TYPE CLASS AROMA CHAR ...
CLASSKEY CLASS AROMA INTEGER ...
Examine the contents of this table by executing the command. There are many more
columns in the result set than shown here.
Section 9. Summary
This tutorial introduced the retail group of tables and suggested some typical
business question that IBM DB2 9 can be used to answer. These tables were
created to show an environment where:
• There are few tables

• Column names use the analyst's vocabulary
• Columns are reflective of the natural dimension of the business.
The bulk of this series consists of detailed examples that show how to write SQL
queries to answer business questions. Most of these examples are based on the
Aroma retail group of tables. The few exceptions are where very small tables are
introduced to demonstrate specific concepts.
The most commonly used data types were described in this tutorial:
Numbers
Character String
Graphic String

Binary String
Datetime Values
Null Value
XML

Downloads
Description Name Size Download
method
Aroma Database Aroma_Data.zip 1MB HTTP
Information about download methods

Resources
Learn
• Read the "DB2 XML evaluation guide" (developerWorks, June 2006), a
step-by-step tutorial introducing the reader to the DB2 Viper data server on
Windows platforms using the XML storage and searching (SQL/XML, XQuery)
capabilities available to support next-generation applications.
• Check out this article and "Get off to a fast start with DB2 Viper"
(developerWorks, March 2006).
• View this article series' "Appendix A" (developerWorks, August 2006).
• Learn how to "Query DB2 XML data with XQuery" (developerWorks, April
2006).
• Learn how to "Query DB2 XML data with SQL" (developerWorks, March 2006).
• Read the IBM Systems Journal and celebrate 10 years of XML.
• Refer to the SQL Reference, Vol 1 for additionanl information.
• Refer to the SQL Reference, Vol 2 for additionanl information.
• Refer to the DB2 information Center for troubleshooting.
Get products and technologies
• Now you can use DB2 for free. Download DB2 Express-C, a no-charge version
of DB2 Express Edition for the community that offers the same core data
features as DB2 Express Edtion and provides a solid base to build and deploy
applications.
Discuss
• Participate in the discussion forum for this content.
• Visit the DB2 9 On-line Support Forum.
About the authors

Pat Moffatt
Pat Moffatt is the Information Management Program Manager for the
IBM Academic Initiative. Through the Academic Initiative program, she
ensures that appropriate Information Management resources are made
available to help faculty integrate Information Management software
into their curriculum. To learn more about this program, visit
www.ibm.com/university/data.

Bruce Creighton
Bruce Creighton is a Skills Segment Planner in the Information
Management Education Planning and Development department. In this
role, he plans investment in educational content and balances the
investment between areas where IBM can attain revenue and those
where the requirement for skills development are important enough to
provide free education.
Jessica Cao
Jessica Cao is an Arts and Science and Computer Science student at
McMaster University. She expects to complete her combined honours
degree in April 2009. Jessica is working in IBM Toronto lab's DB2
Information Management Skills Channel Planning and Enablement
Program to take advantage of her interest in programming, editing, and
writing.
Trademarks
IBM, DB2, Universal Database, OS/2, and pureXML are registered trademarks of
IBM Corporation in the United States and other countries.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft
Corporation in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Linux is a registered trademark of Linus Torvalds in the United States, other
countries, or both.


SQL and Xquery Tutorial For Ibm Db2, Part 1

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SQL and Xquery Tutorial For Ibm Db2, Part 1

Uploaded by

Copyright:

Available Formats

SQL and XQuery tutorial for IBM DB2, Part 1:

Introduction to Aroma and SQL

Pat Moffatt (pmoffatt@ca.ibm.com)

Bruce Creighton (bcreight@ca.ibm.com)

Section 1. Before you start

About this series

Introduction to Aroma and SQL Trademarks

• A business question, expressed in everyday language

About this tutorial

These tables were created to show an environment where:

• There are few tables

Introduction to Aroma and SQL Trademarks

Installing DB2 Express-C 9

1. Navigate to the folder containing the downloaded file -

2. Unzip the file.

5. Click on Install New under DB2 Express.

7. Choose a Typical installation and click Next.

9. Verify the installation directory and click Next.

10. In the "Configure DB2 instances" screen, click Next.

Introduction to Aroma and SQL Trademarks

14. To simplify installation, uncheck Set up your DB2 server to send

Installing the Aroma database

1. Ensure DB2 Express-C 9 is installed.

3. Execute create_aroma.bat in the Command Window.

Introduction to Aroma and SQL Trademarks

db2 create db aromadb using codeset utf-8 territory us

Section 2. Aroma database group of tables

Figure 1. Retail group of tables

Introduction to Aroma and SQL Trademarks

Introduction to Aroma and SQL Trademarks

Section 3. Basic Aroma tables

• Business questions are easy to express as SQL queries

Aggregated data is typical of data warehouses. The idea is to summarize data so

Period, Product, and Class dimensions

Perkey Date Day Week Month Qtr Year

Product and Class Tables

Introduction to Aroma and SQL Trademarks

Classkey Prodkey Prod_Name Pkg_Type

Classkey Class_Type Class_Desc

Store, Market, and Promotion tables

Store and Market tables

Introduction to Aroma and SQL Trademarks

foreign-key reference to the Market table.

Storekey Mktkey Store_Type Store_NameStreet City State Zip

Mktkey Hq_city Hq_state District Region

Promokey Promo_Type Promo_Desc Value Start_Date End_Date

Introduction to Aroma and SQL Trademarks

3 100 Aroma catalog 1.00 2004-03-01 2004-03-31

Perkey Classkey Prodkey Storekey Promokey Quantity Dollars Comments

Introduction to Aroma and SQL Trademarks

The primary-key definition is a combination of values from five columns:

perkey, classkey, prodkey, storekey, promokey

About the Sales table

Multipart primary key

perkey, classkey, prodkey, storekey, promokey

Section 4. What is SQL?

Structured Query Language

Introduction to Aroma and SQL Trademarks

manipulating data in a relational database. All relational database management

Here is some more information about SQL:

Commonly asked questions

Introduction to Aroma and SQL Trademarks