DB_CREATE_FILE_DEST

DB_CREATE_ONLINE_LOG_n

USER_DUMP_DEST

LOG_ARCHIVE_DEST

They indicate an optimized execution plan.

They may be able to be tuned to use an index

The full-table scan should be normalized from the database design

A full-table scan is always sub-optimal.

/ '

• '

• '

= '

Primary key access

Access via unique index

Table access by ROWID

Full table scan

8

3

2

4

Indexes are only used in special cases

Indexes are used to make table storage more efficient

Indexes rarely make a difference in SQL performance

Indexes exist solely to improve query speed

SQL cannot support object-orientation

The same query can be written in many ways, each with vastly different execution plans.

SQL syntax is too difficult for non-computer professionals to use

SQL creates excessive locks within the database

The user had to have knowledge of the table and index structures

Navigational data access was far slower than declarative access.

Navigational access languages required the coder to embed their queries inside a procedural language shell.

Navigational languages were far slower then SQL

Range

Freelist

Hash

Index

True

False

True

False

True

False

True

False

True

False

True

False

HASH

MODULUS

RANGE

RANDOM

FOR EACH ROW trigger on the EMP table

Statement-level Trigger on the EMP table

FOR EACH ROW trigger on the AUDIT_TABLE table

Statement-level Trigger on the AUDIT_TABLE

Trigger type

Trigger body

Trigger event

Trigger Timing

DML trigger

Invalid Trigger

Application Trigger

System Event trigger

1

10

none

Value equal to number of rows in EMP table