Chapter01 1
Chapter01 1
Seventh Edition
Chapter 1
Databases and Database
Users
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Learning Objectives
1.1 Types of Databases and Database Applications
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Types of Databases and Database Applications
• Traditional Applications:
– Numeric and Textual Databases
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Recent Developments (1 of 2)
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Recent Developments (2 of 2)
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Basic Definitions
• Database:
– A collection of related data.
• Data:
– Known facts that can be recorded and have an implicit meaning.
• Mini-world:
– Some part of the real world about which data is stored in a database.
For example, student grades and transcripts at a university.
• Database System:
– The DBMS software together with the data itself. Sometimes, the
applications are also included.
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Impact of Databases and Database Technology
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Figure 1.1 Simplified database system environment
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Typical DBMS Functionality
• Define a particular database in terms of its data types, structures,
and constraints
• Construct or Load the initial database contents on a secondary
storage medium
• Manipulating the database:
– Retrieval: Querying, generating reports
– Modification: Insertions, deletions and updates to its content
– Accessing the database through Web applications
• Processing and Sharing by a set of concurrent users and
application programs – yet, keeping all data valid and consistent
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Application Activities Against a Database
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Additional DBMS Functionality
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Example of a Database (with a Conceptual
Data Model) (1 of 2)
• Mini-world for the example:
– Part of a UNIVERSITY environment.
• Some mini-world entities:
– STUDENTs
– COURSEs
– SECTIONs (of COURSEs)
– (academic) DEPARTMENTs
– INSTRUCTORs
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Example of a Database (with a Conceptual
Data Model) (2 of 2)
• 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
• Note: The above entities and relationships are typically
expressed in a conceptual data model, such as the
ENTITY-RELATIONSHIP data model (see Chapters 3, 4)
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Figure 1.2 Example of a simple database (1 of 4)
COURSE
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Figure 1.2 Example of a simple database (2 of 4)
SECTION
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Figure 1.2 Example of a simple database (3 of 4)
GRADE_REPORT
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Figure 1.2 Example of a simple database (4 of 4)
PREREQUISITE
Course_number Prerequisite_number
CS3380 CS3320
CS3380 MATH2410
CS3320 CS1310
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Main Characteristics of the Database
Approach (1 of 3)
• Self-describing nature of a database system:
– A DBMS catalog stores the description of a particular database
(e.g. data structures, types, and constraints)
– The description is called meta-data*.
– This allows the DBMS software to work with different database
applications.
• Insulation between programs and data:
– Called program-data independence.
– Allows changing data structures and storage organization
without having to change the DBMS access programs.
* Some newer systems such as a few NOSQL systems need no meta-
data: they store the data definition within its structure making it self
describing
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Figure 1.3 Example of a simplified
database catalog (1 of 2)
RELATIONS
Relation_name No_of_columns
STUDENT 4
COURSE 4
SECTION 5
GRADE_REPORT 3
PREREQUISITE 2
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Figure 1.3 Example of a simplified
database catalog (2 of 2)
COLUMNS
Note: Major_type is defined as an enumerated type with all known majors. XXXXNNNN is
used to define a type with four alphabetic characters followed by four numeric digits.
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Main Characteristics of the Database
Approach (2 of 3)
• Data Abstraction:
– A data model is used to hide storage details and
present the users with a conceptual view of the
database.
– Programs refer to the data model constructs rather
than data storage details
• Support of multiple views of the data:
– Each user may see a different view of the database,
which describes only the data of interest to that user.
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Main Characteristics of the Database
Approach (3 of 3)
• Sharing of data and multi-user transaction
processing:
– Allowing a set of concurrent users to retrieve from and to
update the database.
– Concurrency control within the DBMS guarantees that
each transaction is correctly executed or aborted
– Recovery subsystem ensures each completed transaction
has its effect permanently recorded in the database
– OLTP (Online Transaction Processing) is a major part of
database applications. This allows hundreds of concurrent
transactions to execute per second.
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Database Users
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Database Users – Actors on the Scene (1of 2)
• Actors on the scene
– Database administrators:
▪ Responsible for authorizing access to the database, for
coordinating and monitoring its use, acquiring software
and hardware resources, controlling its use and
monitoring efficiency of operations.
– Database Designers:
▪ Responsible to define the content, the structure, the
constraints, and functions or transactions against the
database. They must communicate with the end-users
and understand their needs.
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Database End Users (1 of 2)
• Actors on the scene
– End-users: They use the data for queries, reports and some of
them update the database content. End-users can be
categorized into:
▪ Casual: access database occasionally when needed
▪ Naïve or Parametric: they make up a large section of the
end-user population.
– They use previously well-defined functions in the form of
“canned transactions” against the database.
– Users of Mobile Apps mostly fall in this category
– Bank-tellers or reservation clerks are parametric users
who do this activity for an entire shift of operations
– Social Media Users post and read information from
websites
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Database End Users (2 of 2)
• Sophisticated:
– These include business analysts, scientists, engineers,
others thoroughly familiar with the system capabilities.
– Many use tools in the form of software packages that work
closely with the stored database.
• Stand-alone:
– Mostly maintain personal databases using ready-to-use
packaged applications.
– An example is the user of a tax program that creates its
own internal database.
– Another example is a user that maintains a database of
personal photos and videos.
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Database Users – Actors on the Scene (2 of 2)
• System Analysts and Application Developers
This category currently accounts for a very large proportion of
the IT work force.
– System Analysts: They understand the user requirements of
naïve and sophisticated users and design applications
including canned transactions to meet those requirements.
– Application Programmers: Implement the specifications
developed by analysts and test and debug them before
deployment.
– Business Analysts: There is an increasing need for such
people who can analyze vast amounts of business data and
real-time data (“Big Data”) for better decision making related
to planning, advertising, marketing etc.
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Database Users – Actors behind the Scene
• System Designers and Implementors: Design and implement
DBMS packages in the form of modules and interfaces and test
and debug them. The DBMS must interface with applications,
language compilers, operating system components, etc.
• Tool Developers: Design and implement software systems
called tools for modeling and designing databases, performance
monitoring, prototyping, test data generation, user interface
creation, simulation etc. that facilitate building of applications and
allow using database effectively.
• Operators and Maintenance Personnel: They manage the
actual running and maintenance of the database system
hardware and software environment.
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Advantages of Using the Database Approach (1 of 2)
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Advantages of Using the Database Approach (2 of 2)
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Additional Implications of Using the
Database Approach (1 of 2)
• Potential for enforcing standards:
– This is very crucial for the success of database
applications in large organizations. Standards refer
to data item names, display formats, screens, report
structures, meta-data (description of data), Web page
layouts, etc.
• Reduced application development time:
– Incremental time to add each new application is
reduced.
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Additional Implications of Using the
Database Approach (2 of 2)
• Flexibility to change data structures:
– Database structure may evolve as new requirements
are defined.
• Availability of current information:
– Extremely important for on-line transaction systems
such as shopping, airline, hotel, car reservations.
• Economies of scale:
– Wasteful overlap of resources and personnel can be
avoided by consolidating data and applications across
departments.
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Historical Development of Database
Technology (1 of 3)
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Historical Development of Database
Technology (2 of 3)
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Historical Development of Database
Technology (3 of 3)
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Extending Database Capabilities (2 of 3)
• Background since the advent of the 21st Century:
– First decade of the 21st century has seen tremendous
growth in user generated data and automatically
collected data from applications and search engines.
– Social Media platforms such as Facebook and Twitter
are generating millions of transactions a day and
businesses are interested to tap into this data to
“understand” the users
– Cloud Storage and Backup is making unlimited
amount of storage available to users and applications
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Extending Database Capabilities (3 of 3)
• Emergence of Big Data Technologies and NOSQL databases
– New data storage, management and analysis technology was
necessary to deal with the onslaught of data in petabytes a day (10**15
bytes or 1000 terabytes) in some applications – this started being
commonly called as “Big Data”.
– Hadoop (which originated from Yahoo) and Mapreduce Programming
approach to distributed data processing (which originated from Google)
as well as the Google file system have given rise to Big Data
technologies (Chapter 25). Further enhancements are taking place in
the form of Spark based technology.
– NOSQL (Not Only SQL- where SQL is the de facto standard language
for relational DBMSs) systems have been designed for rapid search and
retrieval from documents, processing of huge graphs occurring on social
networks, and other forms of unstructured data with flexible models of
transaction processing (Chapter 24).
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
When not to use a DBMS (1 of 2)
• Main inhibitors (costs) of using a DBMS:
– High initial investment and possible need for additional
hardware.
– Overhead for providing generality, security, concurrency control,
recovery, and integrity functions.
• When a DBMS may be unnecessary:
– If the database and applications are simple, well defined, and not
expected to change.
– If access to data by multiple users is not required.
• When a DBMS may be infeasible:
– In embedded systems where a general purpose DBMS may not
fit in available storage
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
When not to use a DBMS (2 of 2)
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Chapter Summary
• Types of Databases and Database Applications
• Basic Definitions
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved
Copyright
Copyright © 2016, 2011, 2007 Pearson Education, Inc. All Rights Reserved