1 / 10

Database Environment

Database Environment. CPSC 356 Database Ellen Walker Hiram College. Three Levels of Abstraction. External level How users perceive the data Multiple views Conceptual level Description of data and relationships Internal (Physical) level How the data is physically stored.

neorah
Download Presentation

Database Environment

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Database Environment CPSC 356 Database Ellen Walker Hiram College

  2. Three Levels of Abstraction • External level • How users perceive the data • Multiple views • Conceptual level • Description of data and relationships • Internal (Physical) level • How the data is physically stored

  3. Data Independence • Logical Data Independence • External views do not change when conceptual schema changes • Existing applications do not need to be rewritten to accommodate new ones • Physical Data Independence • Conceptual schema does not change when internal schema changes (e.g. new server)

  4. Describing the Data • DDL (Data Definition Language) • Detailed definition of database schema (metadata) • Too low-level (and database-specific) for good modeling! • Object-based model (entity-relationship) • Record-based model (relational)

  5. Data Manipulation Languages • Commands to access and update databases • Procedural describes how to retrieve the data • Example: relational algebra • Analogy: Fortran • Non-procedural describes what data to retrieve • Example: SQL • Analogy: Prolog

  6. Data Models • Structural part • How the database is constructed • Manipulative part • What operations on data are allowed • Integrity constraints • Ensuring the data remains accurate

  7. Object-Based Data Models • Entity-Relationship • Semantic • Functional • Object-Oriented

  8. Record-Based Data Models • Relational • Network • Hierarchical

  9. What Should a Database Provide? • Ability to store, retrieve and update data • Access to metadata (e.g. names & types) • Transaction processing (all or none) • Concurrency control • Recovery from damage • Authentication & related security

  10. What Should a Database Provide? (cont’d) • Support for networking & communications • Integrity assurance • Independence of programs from data • Utility services • Import, export, monitoring, usage analysis, garbage collection, etc.

More Related