INFORMATION MANAGEMENT

MODULE 8: Advanced SQL and Data Control

Language (DCL)
 MODULE 8 SUBTOPIC 1

ADVANCED SQL
 MODULE 8

OBJECTIVES

■At the end of the chapter, the learner should be able to:
• Define terms
• Write single and multiple table SQL queries
• Define and use three types of joins
• Write noncorrelated and correlated subqueries
• Differentiate system privileges from object privileges
• Grant privileges on tables
• Grant roles
• Distinguish between privileges and roles
EMPLOYEES DEPARTMENTS

…
Use a join to query data from more than one table:
SELECT table1.column, table2.column
FROM table1
[NATURAL JOIN table2] |
[JOIN table2 USING (column_name)] |
[JOIN table2
ON (table1.column_name = table2.column_name)]|
[LEFT|RIGHT|FULL OUTER JOIN table2
ON (table1.column_name = table2.column_name)]|
[CROSS JOIN table2];

Database Systems 1
Join–a relational operation that causes two or more tables
with a common domain to be combined into a single table or
view

• Equi-join–a join in which the joining condition is based on equality between

values in the common columns; common columns appear redundantly in the
result table

• Natural join–an equi-join in which one of the duplicate columns is eliminated in the result table

The common columns in joined tables are usually the primary key
of the dominant table and the foreign key of the dependent table in
1:M relationships.

Database Systems 1
• Outer join–a join in which rows that do not have matching values in
common columns are nonetheless included in the result table (as
opposed to inner join, in which rows must have matching values in
order to appear in the result table)

• Union join–includes all columns from each table in the join, and an
instance for each row of each table

Database Systems 1
Figure 7-2
Visualization of different join types with results returned in shaded area
The following slides create tables for this enterprise data model

(from Chapter 1, Figure 1-3)

Figure 7-1 Pine Valley Furniture Company Customer_T and
Order_T tables with pointers from customers to their orders

These tables are used in queries that follow

For each customer who placed an order, what is the customer’s name and
order number?

Customer ID
appears twice in the
result

Database Systems 1
INNER JOIN clause is an alternative to WHERE clause, and is
used to match primary and foreign keys.

An INNER join will only return rows from each table that have
matching rows in the other.

This query produces same results as previous equi-join example.

For each customer who placed an order, what is the customer’s name and
order number?

Join involves multiple tables in FROM clause

Note: From Fig. 7-1, you see that

ON clause performs the
equality check for common
columns of the two tables
only 10 Customers have links with
orders.
➔ Only 10 rows will be returned from
this INNER join

Database Systems 1
List the customer name, ID number, and order number for all customers.
Include customer information even for customers that do have an order.

LEFT OUTER JOIN clause Unlike INNER join, this

causes customer data to will include customer
appear even if there is rows with no matching
no corresponding order order rows
data

Database Systems 1
Outer Join
Results

Unlike
INNER join,
this will
include
customer
rows with
no matching
order rows
Assemble all information necessary to create an invoice for order number
1006

Four
tables
involved
in this
join
Each pair of tables requires an equality-check condition in the
WHERE clause, matching primary keys against foreign keys.

Database Systems 1
Figure 7-4 Results from a four-table join (edited for readability)

From CUSTOMER_T table

From ORDER_T table From PRODUCT_T table

 The same table is
used on both sides of
the join;
distinguished using
table aliases

Self-joins are usually used on tables with unary relationships.

Figure 7-5 Example of a self-join
Subquery–placing an inner query (SELECT statement) inside an outer query
Options:
• In a condition of the WHERE clause
• As a “table” of the FROM clause
• Within the HAVING clause
Subqueries can be:
• Noncorrelated–executed once for the entire outer query

• Correlated–executed once for each row returned by the outer query

Database Systems 1
Show all customers who have placed an order

• Show all customers who have placed an order

The IN operator will
test to see if the
CUSTOMER_ID
value of a row is
included in the list
returned from the
subquery

Subquery is embedded in parentheses. In

this case it returns a list that will be used
in the WHERE clause of the outer query

Database Systems 1
Some queries could be accomplished by either a join or a subquery

Join version

Subquery version

Database Systems 1
Figure 7-6 Graphical depiction of two ways to answer a query
with different types of joins
Figure 7-6 Graphical depiction of two ways to answer a query with
different types of joins
Noncorrelated subqueries:
• Do not depend on data from the outer query
• Execute once for the entire outer query
Correlated subqueries:
• Make use of data from the outer query
• Execute once for each row of the outer query
• Can use the EXISTS operator

Database Systems 1
 Figure 7-8a Processing a noncorrelated subquery

26

A noncorrelated subquery processes completely before the outer query begins.

Show all orders that include furniture finished in natural ash.

The EXISTS operator will return a

TRUE value if the subquery
resulted in a non-empty set,
otherwise it returns a FALSE

➔ A correlated subquery always refers

to an attribute from a table referenced in
the outer query

Database Systems 1
 Figure 7-8b
Processing a
correlated Subquery refers to outer-
subquery query data, so executes once
for each row of outer query

Note: Only the

orders that
involve
products with
Natural Ash will
be included in
the final
results.

28
Show all products whose standard price is higher than the average price

One column of the subquery is an

Subquery forms the derived
table used in the FROM clause
of the outer query
aggregate function that has an
alias name. That alias can then be
referred to in the outer query.

The WHERE clause normally cannot include aggregate functions, but

because the aggregate is performed in the subquery its result can be used in
the outer query’s WHERE clause.

Database Systems 1
Combine the output (union of multiple queries) together into a single result
table

First query

Combine

Second query

Database Systems 1
This is available with newer
versions of SQL, previously
not part of the standard
Figure 7-10
• Be familiar with the data model (entities and relationships)
• Understand the desired results
• Know the attributes desired in results
• Identify the entities that contain desired attributes
• Review ERD
• Construct a WHERE equality for each link
• Fine tune with GROUP BY and HAVING clauses if needed
• Consider the effect on unusual data

Database Systems 1
• Instead of SELECT *, identify the specific attributes in the SELECT
clause; this helps reduce network traffic of result set
• Limit the number of subqueries; try to make everything done in a single
query if possible
• If data is to be used many times, make a separate query and store it as a
view

Database Systems 1
• Understand how indexes are used in query processing
• Keep optimizer statistics up-to-date
• Use compatible data types for fields and literals
• Write simple queries
• Break complex queries into multiple simple parts
• Don’t nest one query inside another query
• Don’t combine a query with itself (if possible avoid self-joins)

Database Systems 1
• Create temporary tables for groups of queries
• Combine update operations
• Retrieve only the data you need
• Don’t have the DBMS sort without an index
• Learn!
• Consider the total query processing time for ad hoc queries

Database Systems 1
END OF SUBTOPIC 1
 MODULE 8 SUBTOPIC 2

DATA CONTROL LANGUAGE

(DCL)
 MODULE 8

OBJECTIVES

■At the end of the chapter, the learner should be able to:
• Differentiate system privileges from object privileges
• Grant privileges on tables
• Grant roles
• Distinguish between privileges and roles
 Database
administrator

Username and password

Privileges

Users
• Database security:
- System security
- Data security
• System privileges: Performing a particular action within the
database
• Object privileges: Manipulating the content of the database
objects
• Schemas: Collection of objects such as tables, views, and
sequences

Database Systems 1
•More than 100 privileges are available.
•The database administrator has high-level system privileges
for tasks such as:
• Creating new users
• Removing users
• Removing tables
• Backing up tables

Database Systems 1
• The database administrator (DBA) creates users with the CREATE USER statement.

CREATE USER user

IDENTIFIED BY password;

CREATE USER demo

IDENTIFIED BY demo;

Database Systems 1
• After a user is created, the DBA can grant specific system privileges to that user.
GRANT privilege [, privilege...]
TO user [, user| role, PUBLIC...];
• An application developer, for example, may have the following system privileges:
• CREATE SESSION
• CREATE TABLE
• CREATE SEQUENCE
• CREATE VIEW
• CREATE PROCEDURE

Database Systems 1
The DBA can grant specific system privileges to a user.

GRANT create session, create table,

create sequence, create view
TO demo;

Database Systems 1
Give a user authority to pass along system privileges:

GRANT create session, create table

TO demo
WITH ADMIN OPTION;

Database Systems 1
 Users

Manager

Privileges

Allocating privileges Allocating privileges

without a role with a role

Database Systems 1
• Create a role:
CREATE ROLE manager;

• Grant privileges to a role:

GRANT create table, create view
TO manager;

• Grant a role to users:

GRANT manager TO BELL, KOCHHAR;

Database Systems 1
• The DBA creates your user account and initializes your password.
• You can change your password by using the ALTER USER statement.

ALTER USER demo

IDENTIFIED BY employ;

Database Systems 1
Object
privilege Table View Sequence

ALTER

DELETE

INDEX

INSERT

REFERENCES

SELECT

UPDATE
• Object privileges vary from object to object.
• An owner has all the privileges on the object.
• An owner can give specific privileges on that owner’s object.

GRANT object_priv [(columns)]

ON object
TO {user|role|PUBLIC}
[WITH GRANT OPTION];

Database Systems 1
• Grant query privileges on the EMPLOYEES table:
GRANT select
ON employees
TO demo;

• Grant privileges to update specific columns to users and roles:

GRANT update (department_name, location_id)

ON departments
TO demo, manager;

Database Systems 1
• Give a user authority to pass along privileges:
GRANT select, insert
ON departments
TO demo
WITH GRANT OPTION;

• Allow all users on the system to query data from Alice’s DEPARTMENTS table:

GRANT select
ON alice.departments
TO PUBLIC;

Database Systems 1
Data Dictionary View Description

ROLE_SYS_PRIVS System privileges granted to roles

ROLE_TAB_PRIVS Table privileges granted to roles

USER_ROLE_PRIVS Roles accessible by the user

USER_SYS_PRIVS System privileges granted to the user

USER_TAB_PRIVS_MADE Object privileges granted on the user’s objects

USER_TAB_PRIVS_RECD Object privileges granted to the user

USER_COL_PRIVS_MADE Object privileges granted on the columns of the user’s
objects

USER_COL_PRIVS_RECD Object privileges granted to the user on specific

columns
• You use the REVOKE statement to revoke privileges granted to other users.
• Privileges granted to others through the WITH GRANT OPTION clause are also
revoked.

REVOKE {privilege [, privilege...]|ALL}

ON object
FROM {user[, user...]|role|PUBLIC}
[CASCADE CONSTRAINTS];

Database Systems 1
Revoke the SELECT and INSERT privileges given to the demo user on the
DEPARTMENTS table.

REVOKE select, insert

ON departments
FROM demo;

Database Systems 1
In this lesson, you should have learned about statements that control
access to the database and database objects.

Statement Action

CREATE USER Creates a user (usually performed by a DBA)

GRANT Gives other users privileges to access the objects

CREATE ROLE Creates a collection of privileges (usually performed by a DBA)

ALTER USER Changes a user’s password

REVOKE Removes privileges on an object from users

END OF MODULE 8
• Taylor, A. G. (2019). SQL for dummies (9th ed.). Hoboken, NJ: For
Dummies.
• Harrington, J. (2016). Relational Database Design and Implementation
(4th Edition). Morgan Kaufmann
• Juric, N., Vrbsky, S., Nestorov, S. (2016). Database Systems: Introduction
to Databases and Data Warehouses. Prospect Press
• Kroenke, D. M., & Auer, D. J. (2016). Database Concepts. Pearson.
• Sullivan, D. (2015). NoSQL for Mere Mortals (1st ed.). Boston: Addison-
Wesley.
• Hoffer, J., Ramesh, V., Topi, H. (2013). Modern Database Management 11th
Edition, Prentice Hall.

Introduction to Programming