Comprehensive Notes — Chapter 11 “Databases”

Learning Objectives

  • After studying these notes, you should be able to:

    • Distinguish between the physical and logical views of data.

    • Describe logical data‐organization units: characters, fields, records, tables, databases.

    • Explain key (primary) fields and how they integrate tables.

    • Compare batch processing\text{batch processing} vs. real-time (online) processing\text{real-time (online) processing}.

    • State the need for databases and define DBMS software.

    • Compare the five common database models: hierarchical, network, relational, multidimensional, and object-oriented.

    • Differentiate among individual, company, distributed, and commercial databases.

    • Discuss strategic uses (data warehouses, data mining) and security concerns (privacy, unauthorized access, firewalls).

Introduction & Importance

  • Modern life produces enormous digital footprints (credit-card purchases, social-media check-ins, DNA samples).

  • Databases store, organize, and make sense of virtually all organizational information (schools, hospitals, banks, governments).

  • Knowing database concepts lets you

    • locate accurate information quickly,

    • understand data-driven decision making,

    • protect personal privacy.

Two Perspectives on Data

  • Physical View

    • Focus: actual format & storage location (bits → bytes → characters via Unicode, etc.).

    • Only highly specialized professionals deal with this view.

  • Logical View

    • Focus: meaning, content, context.

    • Concern of end users & most professionals.

    • All subsequent sections adopt this perspective.

Logical Data Organization

  • Data is grouped hierarchically (simple → complex):

    • Character: single letter, number, or symbol.

    • Field: group of related characters representing one attribute (e.g., Last Name = "Brown").

    • Record: collection of related fields describing one entity (e.g., payroll record).

    • Table (File/Relation): collection of related records (e.g., Payroll Table).

    • Database: integrated collection of logically related tables (e.g., Personnel Database contains Payroll & Benefits tables).

Key (Primary) Field

  • Unique identifier for each record (Employee ID, Driver’s License No.).

  • Allows relationships between tables (shared key = foreign key in relational terms).

Processing Approaches

Batch Processing ("later")

  • Data collected over hours/days/weeks and processed as a batch.

  • Example: monthly credit-card statements.

  • Pros: efficient on legacy systems; cons: information lag.

Real-Time (Online) Processing ("now")

  • Data processed instantly as transactions occur.

  • Example: ATM withdrawal validates balance, dispenses cash, updates account immediately.

  • Enabled by direct-access storage devices.

Need for Databases & Advantages

  • Data Redundancy (same info stored multiple places) causes storage waste & update anomalies.

  • Data Integrity problems arise when redundant copies disagree ("Main St." vs. "Main Street").

  • Databases solve by providing:

    • Sharing: departments access common pool.

    • Security: access rights & passwords limit exposure.

    • Reduced Redundancy: single authoritative record.

    • Higher Integrity: single update propagates.

Database Management Systems (DBMS)

  • Specialized software to create, modify, and access databases (e.g., Microsoft Access, enterprise Oracle servers).

  • Five Subsystems:

    1. DBMS Engine – bridges logical requests ↔ physical data location.

    2. Data Definition Subsystem – defines logical structure via a data dictionary (schema): field names, types, sizes, defaults.

    3. Data Manipulation Subsystem – tools for maintenance (add, delete, edit) & analysis; includes

    • Query-By-Example (QBE),

    • Structured Query Language (SQL).

    1. Application Generation Subsystem – wizards/languages to build data-entry forms & interfaces (works with languages like C++, Visual Basic).

    2. Data Administration Subsystem – oversees security, backup, recovery, performance; handled by Database Administrators (DBAs).

  • Processing Rights: DBA-assigned permissions defining who may read/insert/delete/update which data.

  • Data Maintenance: ongoing editing to keep database current.

Database Models

Model

Core Idea

Relationship Rules

Strengths

Limitations

Hierarchical

Records in nodes (tree); parent → many children

One-to-many

Simple, fast for predictable paths

Rigid: each child one parent; deleting parent deletes children

Network

Nodes with extra pointers

Many-to-many

Flexible traversal; avoids duplication

Complex pointers; harder maintenance

Relational

Data in tables (rows=records, columns=fields)

Related by shared key fields

Simplicity; add/delete/modify easily; dominant on PCs & servers

May be slower for complex, multidimensional queries

Multidimensional

Extends tables to 3-D+ data cubes

Cells store measures; dimensions = sides

Intuitive analytics; fast OLAP queries

More storage; complexity

Object-Oriented

Stores objects (data + methods)

Classes → objects

Handles unstructured data; integrates with OO programming; basis of NoSQL

Still emerging; fewer mature tools

Object-Oriented Terminology Applied to Health-Club Example

  • Class = Employee (general definition).

  • Object Instances = Bob (Accountant), Sarah (Salesperson), Omar (Trainer).

  • Attributes = First Name, Address, Specialty, Certification.

  • Methods = Pay() (implemented differently per subclass: salary vs. wage×hours vs. wage×hours+commission).

Types of Databases

  • Individual (Personal-Computer) Database

    • Controlled by single user; stored on personal HDD or LAN share.

    • Uses: salesperson’s client list, freelancer project tracker.

  • Company (Organizational) Database

    • Central server; multiuser via LAN/WAN; foundation of MIS/ERP.

    • Uses: department-store sales records driving bonuses & reorders.

  • Distributed Database

    • Data physically split across geographic sites; linked via networks & database servers (client/server architecture).

    • Example: retail chain with regional servers + headquarters consolidation.

  • Commercial (Information Utility/Data Bank)

    • Massive, subject-focused; access sold to orgs/individuals (membership + usage fee).

    • Examples & content:

    • ProQuest Dialog – business, technical, scientific.

    • Dow Jones Factiva – global news, stocks.

    • LexisNexis – legal news, public records.

Strategic Uses: Data Warehousing & Mining

  • Data Warehouse: centralized, cleaned, historical repository integrating internal & external data sources for analysis.

  • Data Mining: algorithmic search for hidden patterns/relationships (market-basket analysis, fraud detection, customer segmentation).

  • Business information categories held in commercial/public databases:

    • Business directories, demographic data, statistical financials, full-text articles, vast Web indices.

Security Considerations

  • Threats

    • Misuse of sensitive personal data (credit history, medical records) for hiring/promotion.

    • Unauthorized access, viruses, malware.

  • Protections

    • Physical security (guards, biometric scanners—e.g., electronic fingerprint reader).

    • Logical security: firewalls (hardware/software barriers) on WANs, authentication, encryption.

Future Perspective: Crime-Prediction Databases

  • Research correlating behavioral, socioeconomic, and genomic data to forecast violent behavior.

  • Potential expansion to national DNA databases and integration with education, healthcare, insurance records.

  • Ethical Trade-offs

    • Privacy vs. Security\text{Privacy vs. Security}: willingness to surrender personal data to reduce crime.

    • Trust in governmental stewardship and data accuracy.

Careers in IT: Database Administrator (DBA)

  • Role: design structures, tune performance, ensure integrity, manage security & backup.

  • Growing demand across industries.

  • Typical qualifications: Bachelor’s in CS/IS, hands-on DBMS experience, internships.

  • Salary range: 47,00047,000 – 111,000111,000 annually.

  • Advancement: senior DBA, data architect, Chief Technology Officer (CTO).

Concept-Check Questions (Self-Test)

  • List & describe the logical data-organization hierarchy.

  • What distinguishes a key field? Give two examples.

  • Contrast batch vs. real-time processing with a personal example.

  • Provide four advantages databases bring over independent departmental files.

  • Identify the five DBMS subsystems and one tool/function from each.

  • Compare hierarchical, network, and relational models in terms of parent/child relationships.

  • Why are multidimensional databases faster for analytical queries?

  • Explain the four database types with real-world examples.

  • Define data warehouse and data mining; give one use case of each.

  • Describe two database security measures your school or workplace might employ.

Key Terms Glossary

  • Attribute

  • Batch Processing

  • Data Dictionary (Schema)

  • Data Integrity

  • Data Maintenance

  • Data Mining

  • Data Warehouse

  • Database Administrator (DBA)

  • Database Management System (DBMS)

  • Firewalls

  • Key Field (Primary Key)

  • Logical vs. Physical View

  • Multidimensional Database

  • Object-Oriented Database

  • Query-By-Example (QBE)

  • Structured Query Language (SQL)

End of Study Notes