Database management chapter 2 power point

David M. Kroenke and David J. Auer
Database Processing:
Fundamentals, Design, and Implementation
Chapter Two:
Introduction to
Structured Query
Language
2-1KROENKE AND AUER - DATABASE PROCESSING, 12th Edition
© 2012 Pearson Prentice Hall

Chapter Objectives
• To understand the use of extracted data sets in business
intelligence (BI) systems
• To understand the use of ad-hoc queries in business
intelligence (BI) systems
• To understand the history and significance of Structured
Query Language (SQL)
• To understand the SQL SELECT/FROM/WHERE
framework as the basis for database queries
• To create SQL queries to retrieve data from a single
table

Chapter Objectives
• To create SQL queries that use the SQL SELECT,
FROM, WHERE, ORDER BY, GROUP BY, and HAVING
clauses
• To create SQL queries that use the SQL DISTINCT,
AND, OR, NOT, BETWEEN, LIKE, and IN keywords
• To create SQL queries that use the SQL built-in functions
of SUM, COUNT, MIN, MAX, and AVG with and without
the use of a GROUP BY clause

Chapter Objectives
• To create SQL queries that retrieve data from a single
table but restrict the data based upon data in another
table (subquery)
• To create SQL queries that retrieve data from multiple
tables using an SQL join operation

Business Intelligence (BI) Systems
• Business intelligence (BI) systems are
information systems that assist managers
and other professionals:
– Assessment
– Analysis
– Planning
– Control

Ad-Hoc Queries
• Ad-hoc queries:
– Questions that can be answered using
database data
– Example: “How many customers in Portland,
Oregon, bought our green baseball cap?”
– Created by the user as needed, instead of
programmed into an application
– Common in business

Components of a Data Warehouse

Structured Query Language
• Structured Query Language (SQL) was
developed by the IBM Corporation in the late
1970’s.
• SQL was endorsed as a U.S. national standard
by the American National Standards Institute
(ANSI) in 1992 [SQL-92].
• Newer versions exist, and they incorporate XML
and some object-oriented concepts.

SQL As a Data Sublanguage
• SQL is not a full featured programming
language.
– C, C#, Java
• SQL is a data sublanguage for creating
and processing database data and
metadata.
• SQL is ubiquitous in enterprise-class
DBMS products.
• SQL programming is a critical skill.

SQL DDL, DML, and SQL/PSM
• SQL statements can be divided into three
categories:
– Data definition language (DDL) statements
• Used for creating tables, relationships, and other
structures
• Covered in Chapter 7
– Data manipulation language (DML)
statements
• Used for queries and data modification
• Covered in this chapter (Chapter 2)

SQL DDL, DML, and SQL/PSM
– SQL/Persistent Stored Modules (SQL/PSM)
statements
• Add procedural programming capabilities
– Variables
– Control-of-flow statements
• Covered in Chapters:
– 7 (general introduction)
– 10 (SQL Server 2008 R2)
– 10A (Oralce Database 11g)
– 10B (MySQL 5.5)

Cape Codd Outdoor Sports
• Cape Codd Outdoor Sports is a fictitious
company based on an actual outdoor retail
equipment vendor.
• Cape Codd Outdoor Sports:
– Has 15 retail stores in the United States and
Canada.
– Has an online Internet store.
– Has a (postal) mail order department.
• All retail sales are recorded in an Oracle
database.

Cape Codd Retail Sales Structure

Cape Codd Retail Sales Data
Extraction
• The Cape Codd marketing department needs an
analysis of in-store sales.
• The entire database is not needed for this, only an
extraction of retail sales data.
• The data is extracted by the IS department from the
operational database into a separate, off-line
database for use by the marketing department.
• Three tables are used: RETAIL_ORDER,
ORDER_ITEM, and SKU_DATA (SKU = Stock Keeping
Unit).
• The extracted data is converted as necessary:
– Into a different DBMS—Microsoft SQL Server
– Into different columns—OrderDate becomes OrderMonth and
OrderYear.

Extracted
Retail
Sales Data
Format

Retail Sales Extract Tables
[in Microsoft Access 2010]

The SQL SELECT Statement
• The fundamental framework for an SQL
query is the SQL SELECT statement.
– SELECT {ColumnName(s)}
– FROM {TableName(s)}
– WHERE {Condition(s)}
• All SQL statements end with a semi-colon
(;).

Specific Columns on One Table
SELECT Department, Buyer
FROM SKU_DATA;

Specifying Column Order
SELECT Buyer, Department
FROM SKU_DATA;

The DISTINCT Keyword
SELECT DISTINCT Buyer, Department
FROM SKU_DATA;

Selecting All Columns:
The Asterisk (*) Wildcard Character
SELECT *
FROM SKU_DATA;

Specific Rows from One Table
SELECT *
FROM SKU_DATA
WHERE Department = 'Water Sports';
NOTE: SQL wants a plain ASCII single quote: ' NOT ‘ !

Specific Columns and Rows from
One Table
SELECT SKU_Description, Buyer
FROM SKU_DATA
WHERE Department = 'Climbing';

Using Microsoft Access I

Using Microsoft Access II

Using Microsoft Access III

Using Microsoft Access IV

Using Microsoft Access V

Using Microsoft Access—Results

Using Microsoft Access
Saving the Query

Using Microsoft Access
The Named and Saved Query

Using Microsoft SQL Server 2008 R2
The Microsoft SQL Server Management Studio I

Using Microsoft SQL Server 2008 R2
The Microsoft SQL Server Management Studio II

Using Oracle Database 11g
SQL Developer I

Using Oracle Database 11g
SQL Developer II

Using MySQL 5.5
MySQL Workbench I

Using MySQL 5.5
MySQL Workbench II

Sorting the Results—ORDER BY
SELECT *
FROM ORDER_ITEM
ORDER BY OrderNumber, Price;

Sort Order:
Ascending and Descending
SELECT *
FROM ORDER_ITEM
ORDER BY Price DESC, OrderNumber ASC;
NOTE: The default sort order is ASC—does not have to be specified.

WHERE Clause Options—AND
SELECT *
FROM SKU_DATA
WHERE Department = 'Water Sports'
AND Buyer = 'Nancy Meyers';

WHERE Clause Options—OR
SELECT *
FROM SKU_DATA
WHERE Department = 'Camping'
OR Department = 'Climbing';

WHERE Clause Options—IN
SELECT *
FROM SKU_DATA
WHERE Buyer IN ('Nancy Meyers',
'Cindy Lo', 'Jerry Martin');

WHERE Clause Options—NOT IN
SELECT *
FROM SKU_DATA
WHERE Buyer NOT IN ('Nancy Meyers',
'Cindy Lo', 'Jerry Martin');

WHERE Clause Options—
Ranges with BETWEEN
SELECT *
FROM ORDER_ITEM
WHERE ExtendedPrice
BETWEEN 100 AND 200;

Ranges with Math Symbols
SELECT *
FROM ORDER_ITEM
WHERE ExtendedPrice >= 100
AND ExtendedPrice <= 200;

LIKE and Wildcards I
• The SQL keyword LIKE can be combined
with wildcard symbols:
– SQL 92 Standard (SQL Server, MySQL, etc.):
• _ = exactly one character
• % = any set of one or more characters
– Microsoft Access (based on MS DOS)
• ? = exactly one character
• * = any set of one or more characters

LIKE and Wildcards II
SELECT *
FROM SKU_DATA
WHERE Buyer LIKE 'Pete%';

LIKE and Wildcards III
SELECT *
FROM SKU_DATA
WHERE Buyer LIKE '%Tent%';

LIKE and Wildcards IV
SELECT *
FROM SKU_DATA
WHERE SKU LIKE '%2__';

SQL Built-In Functions I
• There are five SQL built-in functions:
– COUNT
– SUM
– AVG
– MIN
– MAX

SQL Built-In Functions II
SELECT SUM(ExtendedPrice)
AS Order3000Sum
FROM ORDER_ITEM
WHERE OrderNumber = 3000;

SQL Built-In Functions III
SELECT SUM(ExtendedPrice) AS OrderItemSum,
AVG(ExtendedPrice) AS OrderItemAvg,
MIN(ExtendedPrice) AS OrderItemMin,
MAX(ExtendedPrice) AS OrderItemMax
FROM ORDER_ITEM;

SQL Built-In Functions IV
SELECT COUNT(*) AS NumberOfRows
FROM ORDER_ITEM;

SQL Built-In Functions V
SELECT COUNT
(DISTINCT Department)
AS DeptCount
FROM SKU_DATA;

Arithmetic in SELECT Statements
SELECT Quantity * Price AS EP,
ExtendedPrice
FROM ORDER_ITEM;

String Functions in SELECT
Statements
SELECT DISTINCT RTRIM (Buyer)
+ ' in ' + RTRIM (Department)
AS Sponsor
FROM SKU_DATA;
NOTE: This SQL statement uses SQL Server 2008 R2 syntax—other DBMS
products use different concatenation and character string operators.

The SQL Keyword GROUP BY I
SELECT Department, Buyer,
COUNT(*) AS
Dept_Buyer_SKU_Count
FROM SKU_DATA
GROUP BY Department, Buyer;

The SQL Keyword GROUP BY II
• In general, place WHERE before GROUP BY.
Some DBMS products do not require that
placement; but to be safe, always put WHERE
before GROUP BY.
• The HAVING operator restricts the groups that
are presented in the result.
• There is an ambiguity in statements that include
both WHERE and HAVING clauses. The results
can vary, so to eliminate this ambiguity SQL
always applies WHERE before HAVING.

The SQL Keyword GROUP BY III
SELECT Department, COUNT(*) AS
Dept_SKU_Count
FROM SKU_DATA
WHERE SKU <> 302000
GROUP BY Department
ORDER BY Dept_SKU_Count;

The SQL Keyword GROUP BY IV
SELECT Department, COUNT(*) AS
Dept_SKU_Count
FROM SKU_DATA
WHERE SKU <> 302000
GROUP BY Department
HAVING COUNT (*) > 1
ORDER BY Dept_SKU_Count;

Querying Multiple Tables:
Subqueries I
SELECT SUM (ExtendedPrice) AS Revenue
FROM ORDER_ITEM
WHERE SKU IN
(SELECT SKU
FROM SKU_DATA
WHERE Department = 'Water Sports');
Note: The second SELECT statement is a subquery.

Subqueries II
SELECT Buyer
FROM SKU_DATA
WHERE SKU IN
(SELECT SKU
FROM ORDER_ITEM
WHERE OrderNumber IN
(SELECT OrderNumber
FROM RETAIL_ORDER
WHERE OrderMonth = 'January'
AND OrderYear = 2011));

Joins I
SELECT Buyer, ExtendedPrice
FROM SKU_DATA, ORDER_ITEM
WHERE SKU_DATA.SKU =
ORDER_ITEM.SKU;

Joins II
SELECT Buyer, SUM(ExtendedPrice)
AS BuyerRevenue
FROM SKU_DATA, ORDER_ITEM
WHERE SKU_DATA.SKU = ORDER_ITEM.SKU
GROUP BY Buyer
ORDER BY BuyerRevenue DESC;

Joins III
SELECT Buyer, ExtendedPrice, OrderMonth
FROM SKU_DATA, ORDER_ITEM, RETAIL_ORDER
WHERE SKU_DATA.SKU = ORDER_ITEM.SKU
AND ORDER_ITEM.OrderNumber =
RETAIL_ORDER.OrderNumber;

Subqueries versus Joins
• Subqueries and joins both process multiple
tables.
• A subquery can only be used to retrieve data
from the top table.
• A join can be used to obtain data from any
number of tables, including the “top table” of the
subquery.
• In Chapter 7, we will study the correlated
subquery. That kind of subquery can do work
that is not possible with joins.

David Kroenke and David Auer
Database Processing
Fundamentals, Design, and Implementation
(11th
Edition)
End of Presentation:
Chapter Two

All rights reserved. No part of this publication may be reproduced, stored in a
retrieval system, or transmitted, in any form or by any means, electronic,
mechanical, photocopying, recording, or otherwise, without the prior written
permission of the publisher. Printed in the United States of America.
Copyright © 2012 Pearson Education, Inc. Copyright © 2012 Pearson Education, Inc.
Publishing as Prentice HallPublishing as Prentice Hall

Database management chapter 2 power point

More Related Content

What's hot (20)

Viewers also liked (20)

Similar to Database management chapter 2 power point (20)

Recently uploaded (20)

Database management chapter 2 power point