1 / 16

CONCEPT OF DATABASE

CONCEPT OF DATABASE. Contents. Database Definition What Is a DBMS? DBMS Purpose of Database System Why Use a DBMS? Levels of Abstraction Example of database Data Independence Data Models Entity-Relationship Model. Database Definition.

liesel
Télécharger la présentation

CONCEPT OF DATABASE

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. CONCEPT OF DATABASE

  2. Contents • Database Definition • What Is a DBMS? • DBMS • Purpose of Database System • Why Use a DBMS? • Levels of Abstraction • Example of database • Data Independence • Data Models • Entity-Relationship Model

  3. Database Definition • A database represents some aspect of the real world, sometimes called the mini-world. • A database is a logically coherent collection of data with some inherit meaning. • A random assortment of data cannot correctly be referred to as a database. • A database is designed, built, and populated with data for a specific purpose. It has an intended group of users and some preconceived applications in which these users are interested back

  4. What Is a DBMS? • A very large, integrated collection of data. • Models real-world enterprise. • Entities (e.g., students, courses) • Relationships • A Database Management System (DBMS) is a software package designed to store and manage databases. back

  5. DBMS • Collection of interrelated data • Set of programs to access the data • DBMS contains information about a particular enterprise • DBMS provides an environment that is both convenient and efficient to use. • Database Applications: • Banking: all transactions • Airlines: reservations, schedules • Universities: registration, grades • Sales: customers, products, purchases • Manufacturing: production, inventory, orders, supply chain • Human resources: employee records, salaries, tax deductions • Databases touch all aspects of our lives back

  6. Purpose of Database System • In the early days, database applications were built on top of file systems • Drawbacks of using file systems to store data: • Data redundancy and inconsistency • Multiple file formats, duplication of information in different files • Difficulty in accessing data • Need to write a new program to carry out each new task • Data isolation — multiple files and formats • Integrity problems • Integrity constraints (e.g. account balance > 0) become part of program code • Hard to add new constraints or change existing ones

  7. Drawbacks of using file systems (cont.) • Atomicity of updates • Failures may leave database in an inconsistent state with partial updates carried out • E.g. transfer of funds from one account to another should either complete or not happen at all • Concurrent access by multiple users • Concurrent accessed needed for performance • Uncontrolled concurrent accesses can lead to inconsistencies • E.g. two people reading a balance and updating it at the same time • Security problems • Database systems offer solutions to all the above problems back

  8. Why Use a DBMS? • Separation of the Data definition and the Program • Abstraction into a simple model • Data independence and efficient access. • Reduced application development time – ad-hoc queries • Data integrity and security. • Uniform data administration. • Concurrent access, recovery from crashes. • Support for multiple different views back

  9. Levels of Abstraction • Many views, single conceptual (logical) schema and physical schema. • Views describe how users see the data. • Conceptual schema defines logical structure. Sometime we separate between conceptual level and logical level • Physical schema describes the files and indexes used. View 1 View 2 View 3 Conceptual Schema Physical Schema

  10. Levels of Abstraction • Physical level describes how a record (e.g., customer) is stored. • Logical level: describes data stored in database, and the relationships among the data. type customer = recordname : string;street : string;city : integer;end; • View level: application programs hide details of data types. Views can also hide information (e.g., salary) for security purposes. back

  11. Example Of database back

  12. Data Independence • Physical Data Independence – the ability to modify the physical schema without changing the application programs • Applications depend on the logical schema • DBA may change physical level (tuning) without affecting applications • The DBMS automatically make the required adjustments, and application programs are not changed (queries may need to be recompiled and optimized…) • Logical Data Independence – the ability to modify the logical schema without changing the application programs • Applications depend on the logical schema via the Views • Can be supported on a limited basis only (if view is not affected) back

  13. Data Models • A collection of modeling tools for describing • data • data relationships • data semantics • data constraints • Entity-Relationship model • Relational model • Other models: • object-oriented model • semi-structured data models (XML) • Older models: network model and hierarchical model back

  14. Entity-Relationship Model Example of schema in the entity-relationship model back

  15. Entity Relationship Model (Cont.) • E-R model of real world • Entities (objects) • E.g. customers, accounts, bank branch • Relationships between entities • E.g. Account A-101 is held by customer Johnson • Relationship set depositor associates customers with accounts • Widely used for database design • Database design in E-R model usually converted to design in the relational model (coming up next) which is used for storage and processing back

  16. THANK YOU ANY QUERIES?? back

More Related