Chapter01-Introduction to Database Management-fr v6 (1)
Page 1: Introduction
McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved.
Chapter 1: Introduction to Database Management
Page 2: Welcome!
Database Technology: crucial to the operation and management of modern organizations.
Major transformation in computing skills required for database management.
Significant time commitment necessary for mastering database concepts.
Exciting journey ahead in database technology.
Page 3: Review Questions 1
Differentiate between data, information, and knowledge.
Explain database characteristics.
Describe DBMS features.
What is ANSI-SPARC Three-Level Architecture?
Explain the concept behind Data Independence.
Discuss the database system environment.
Page 4: Outline
Topics Covered:
Database characteristics
DBMS features
Development of Database Technology
Three Schema Architectures
Organizational impact of DB technology
Page 5: Initial Vocabulary
Data: raw facts about things and events.
Information: transformed data that has value for decision making.
Importance of organizing data for retrieval and maintenance.
Page 6: Example 1-7
No specific content provided.
Page 7: Data VS. Information
Data: e.g., 95 (raw score).
Information: My score on the final exam is 95% (data + context).
Knowledge: I have passed the exam with excellent mark (data/information + meaning interpretation).
Page 8: Data vs. Information: An Example
Data Examples:
331 Brilo Dish Soap - $1.29
833 BK Hill Coffee - $4.99
173 Meow Cat - $0.75
YTD Sales: $9,231.24
Information: YTD SALES of $9,231.24 is the best figure we had in the past 10 years.
Knowledge: Contextualized understanding of data/information within the sales report.
Page 9: Knowledge
Knowledge: know-how, experience, insight, understanding, and contextualized information.
Information: contextualized, categorized, calculated, and condensed data.
Data: facts and figures which relay something specific but are unorganized.
Page 10: Database Characteristics
Database: A collection of persistent data that can be shared and interrelated.
Persistent: Data must reside on stable storage (e.g., magnetic disk).
Shared: Databases support multiple users and uses.
Interrelated: Data stored as separate units can be connected for a comprehensive picture.
Page 11: University Database
Entities: students, faculty, courses, offerings, enrollments.
Relationships: faculty teach offerings, students enroll in offerings, offerings composed of courses.
Page 12: Water Utility Database
Entities: customers, meters, bills, payments, meter readings.
Relationships: bills sent to customers, customers make payments, customers use meters.
Page 13: Database Management System (DBMS)
Definition: Collection of components supporting data acquisition, dissemination, storage, maintenance, retrieval, and formatting.
Types of DBMS:
Enterprise DBMS: Oracle, IBM DB2.
Desktop DBMS: Access.
Open-source DBMS: MySQL.
Embedded DBMS: Reside in application systems/devices (PDAs, smart cards).
Important role in information technology infrastructure.
Page 14: DBMS Features
Key features include:
Database Definition
Non-Procedural Access
Application Development
Procedural Language Interface
Transaction Processing
Database Tuning
Page 15: DBMS Features: Database Definition
Use of SQL and graphical tools to define database structures.
Table: stores collections of entities in a two-dimensional format of columns (fields) and rows (records).
Page 16: DBMS Features: Database Definition
SQL is the industry-standard language for defining tables and relationships, integrity constraints, and data authorization rights.
Microsoft Access provides graphical tools for table and relationship definition.
Page 17: University Database Relationship Window Using Microsoft Access
Diagramming relationships showing how different entities connect in the university database schema.
Page 18: University Database (ERD) Using Visio Professional
Entity-Relationship Diagram (ERD) outlining entities and their relationships in the university database context.
Page 19: DBMS Features: Nonprocedural Access
Queries: Key feature for data access, specifying what to retrieve without detailing how.
SQL SELECT statement is an example of non-procedural access.
Enhances productivity and accessibility for users.
Page 20: Graphical Tool for Nonprocedural Access
Example of a select query interface allowing users to specify desired data fields and criteria without writing code.
Page 21: DBMS Features: Application Development
Form: Document for data entry and display.
Report: Document for formatted display of data.
Use non-procedural access to define requirements for forms and reports.
Page 22: Sample Data Entry Form Faculty Assignment Form
Example of a faculty assignment form for data input.
Page 23: Sample Report: Faculty Work Load Report 2005-2006
Example report summarizing faculty workload metrics, including enrollments and course limits.
Page 24: DBMS Features: Procedural Language Interface
Combines programming languages (e.g., COBOL, Visual Basic) with SQL for batch processing.
Enables customization, automation, and performance improvements.
Page 25: DBMS Features: Transaction Processing
Transaction: unit of work processed reliably without loss of data.
Important for processing high volume repetitive work and managing multiple simultaneous users.
Page 26: DBMS Features: Database Tuning
Tools for monitoring and improving database performance, including reorganization and repair utilities.
Page 27: Database Technology Evolution
Overview of technology evolution through generations from file-based systems to object-oriented databases.
Page 28: DBMS Marketplace
Overview of prominent DBMS in the marketplace:
Enterprise DBMS: Oracle, SQL Server, DB2.
Open Source: MySQL, Firebird, PostgreSQL.
Desktop DBMS: Access and its competitors.
Page 29: Data Independence
Concept that the database should have a separate identity from applications.
Allows changes in database structure without impacting applications using it.
Page 30: Three Schema Architecture
Proposal from the 1970s for data independence:
Schemas: External, Conceptual, Internal levels.
Page 31: ANSI SPARC Three Schema Architecture
Schemas:
External Level: User-specific views.
Conceptual Level: Community view of the overall database.
Internal Level: Physical storage representation.
Page 32: Three Schema Architecture
External Level: User-defined views tailored to specific needs.
Conceptual Level: Represents entire database entities and their relationships.
Page 33: Three Schema Architecture
Internal Level: Physical representation, defining files/collections on storage devices.
Page 34: Objectives of Three-Level Architecture
Ensure data access remains consistent despite changes in views or physical structure.
Page 35: Objectives of Three-Level Architecture
Enable database administrators (DBAs) to alter storage structures without affecting users' experiences or views.
Page 36: ANSI-SPARC Three-Level Architecture
Diagrams outlining the relationships between various schema levels and user views.
Page 37: ANSI-SPARC Three-Level Architecture
External Level: Users' database view relevant to specific tasks.
Conceptual Level: Overview of what data is stored and relationships among them.
Page 38: ANSI-SPARC Three-Level Architecture
Internal Level: Describes how data is physically stored in the computer system.
Page 39: Differences between Three Levels of ANSI-SPARC Architecture
Illustrations showing structural differences between external, conceptual, and internal schema.
Page 40: Data Independence
Logical Data Independence: External schemas' immunity to changes in conceptual schema.
Page 41: Data Independence
Physical Data Independence: Conceptual schema's immunity to changes in the internal schema.
Page 42: Data Independence and ANSI-SPARC Three-Level Architecture
Overview of how schema independence mappings function between external, conceptual, and internal levels.
Page 43: Schema Mappings
Describes how to derive a schema at a higher level from a lower level through mappings.
Page 44: Distributed Processing
Essential due to network computing, allows dispersed systems to cooperate for data access in e-commerce.
Page 45: Client-Server Architecture
Architecture arrangement of clients and servers in network settings to facilitate database interaction.
Page 46: Organizational Roles
Various roles outlined:
Indirect, Parametric, Power, Functional, Technical, and Non-Technical users.
Page 47: Organizational Roles
Descriptions of user roles from passive interaction to active engagement with databases.
Page 48: Organizational Roles
The roles of information systems professionals in database management and development tasks.
Page 49: Database Specialists
Distinction between DBA (Database Administrator) and DA (Data Administrator) roles based on technical skills.
Page 50: The Database System Environment
Overview of the database system environment including management roles and interactions.
Page 51: Summary
Emphasizes the significance of databases and technology in modern organizations and decision making.
Page 52: Review Questions 1
Review activities to reinforce learning on central topics discussed in the chapter.
Page 53: Review Questions 2
Related exam questions focusing on schema architecture and data independence.