Documente Academic
Documente Profesional
Documente Cultură
1.1 Introduction
1.2 An Example
1.3 Characteristics of the Database Approach
1.4 Actors on the Scene
1.5 Workers behind the Scene
1.6 Advantages of Using a DBMS
1.7 Implications of the Database Approach
1.8 When Not to Use a DBMS
1.9 Summary
1-1 1-1
1.1 Introduction
1-3 1-4
1.2 An Example
Mini-world for the example: Part of a UNIVERSITY environment.
Some mini-world entities:
- STUDENTs
- COURSEs
- SECTIONs (of COURSEs)
- (academic) DEPARTMENTs
- INSTRUCTORs
Some mini-world relationships:
- SECTIONs are of specific COURSEs
- STUDENTs take SECTIONs
- COURSEs have prerequisite COURSEs
- INSTRUCTORs teach SECTIONs
- COURSEs are offered by DEPARTMENTs
- STUDENTs major in DEPARTMENTs
1-4 1-5
1-5 1-6
Define UNIVERSITY database
Constraints
The sections that students take must be taught by some instructors.
1-5a 1-7
Construct UNIVERSITY database
Store data on storage medium
˙store data for each student, course, section, grade repot, prerequisite
˙records in various files may be related to one another
1-5b 1-8
1.3 Characteristics of the Database Approach
• File Processing
Each user defines and implements the files needed for a specific application
Redundancy in defining & storing data
• Database Approach
A single repository of data
-Self-describing nature of a database system: A DBMS catalog stores the descripti
on of the database. The description is called meta-data . This allows the DBMS soft
ware to work with different databases.
catalog: structure of each file, type & storage format of each data item, constraints on
data
1-6 1-10
Storage format for a STUDENT record:
Figure 1.3
{
Student transcript view: derived from
STUDENT
SECTION
GRADE-REPORT
Figure 1.4
1-8 1-12
1.4 Actors on the scene:
Persons whose job involves daily use of a large database
1.4.1 Database administrators(DBAs): Responsible for managing the database system,
authorizing access, coordinating & monitoring uses, acquiring resources.
resources ‧database
‧DBMs
1.4.2 Database designers: Responsible for designing the database, identifying the data
to be stored, choosing the structures to represent and store this data.
1.4.3 End Users: The persons that use the database for querying, updating, generating
reports, etc.
‧Casual end users: Occasional users.(middle- or high-level managers)
‧Parametric (or naive) end users: They use pre-programmed canned
transactions to interact continuously with the database. For example, bank
tellers or reservation clerk.
‧Sophisticated end users: Use full DBMS capabilities for implementing
complex applications.
‧Stand-alone users (personal databases)
1.4.4 System Analysts/Application programmers: Design and implement canned
transactions for parametric users.
1-9 1-13
1.5 Workers behind the scene:
Persons whose job involves design, development, operation,
and maintenance of the DBMS software and system environment.
• Tool developers: Design and implement tools that facilitate the use of the
DBMS software. Tools include design tools, performance tools, special
interfaces,etc.
1-10 1-14
1.6 Advantages of Using a DBMs
1.6.1 Controlling Redundancy in data storage and in development and
maintenance efforts.
‧duplication efforts ‧waste space ‧inconsistent
( see 1-12 controlled redundancy)
1-11 1-16
Controlled redundancy (refer to 1-5)
redundancy VS efficiency
Smith
1-12 1-17
1.8 When not to use a DBMS
Main costs of using a DBMS:
- High initial investment in hardware, software,training
and possible need for additional hardware.
- Overhead for providing generality, security, recovery, integrity, an
d
concurrency control.
- Generality that a DBMS provides for defining and processing data.