Chapter 1: Data Models and DBMS Architecture Title: What Goes Around Comes Around Authors: M. Stonebraker, J. Hellerstein Pages: 2-40.

Slides:



Advertisements
Similar presentations
Database Systems: Design, Implementation, and Management Ninth Edition
Advertisements

Chapter 2 Data Models.
©Silberschatz, Korth and Sudarshan4.1Database System Concepts Lecture-1 Database system,CSE-313, P.B. Dr. M. A. Kashem Associate. Professor. CSE, DUET,
CMSC724: Database Management Systems Instructor: Amol Deshpande
Introduction to Databases
1 1 File Systems and Databases. 1 1 Introducing the Database 4Major Database Concepts u Data and information l Data - Raw facts l Information - Processed.
©Silberschatz, Korth and Sudarshan1.1Database System Concepts Chapter 1: Introduction Purpose of Database Systems View of Data Data Models Data Definition.
1 Chapter 2 Database Environment Transparencies © Pearson Education Limited 1995, 2005.
Chapter 1 File Systems and Databases
File Systems and Databases
Chapter 1.3: Data Models and DBMS Architecture Title: Anatomy of a Database System Authors: J. Hellerstein, M. Stonebraker Pages:
Chapter 2 Database Environment. Agenda Three-Level ANSI-SPARC Architecture Database Languages Data Models Functions of DBMS Components of DBMS Teleprocessing.
Ch1: File Systems and Databases Hachim Haddouti
Data Management I DBMS Relational Systems. Overview u Introduction u DBMS –components –types u Relational Model –characteristics –implementation u Physical.
©Silberschatz, Korth and Sudarshan1.1Database System Concepts Chapter 1: Introduction Purpose of Database Systems View of Data Data Models Data Definition.
File Systems and Databases Hachim Haddouti
The University of Akron Dept of Business Technology Computer Information Systems Database Management Approaches 2440: 180 Database Concepts Instructor:
Data Base Management System
RIZWAN REHMAN, CCS, DU. Advantages of ORDBMSs  The main advantages of extending the relational data model come from reuse and sharing.  Reuse comes.
LECTURE 2 DATABASE SYSTEM CONCEPTS AND ARCHITECTURE.
Database Design and Introduction to SQL
Introduction to Data bases concepts
Introduction to Database Concepts
What is a Database? A database is any collection of data.
Database System Concepts and Architecture Lecture # 3 22 June 2012 National University of Computer and Emerging Sciences.
Database System Concepts, 5th Ed. ©Silberschatz, Korth and Sudarshan See for conditions on re-usewww.db-book.com Chapter 1: Introduction.
Week 1 Lecture MSCD 600 Database Architecture Samuel ConnSamuel Conn, Asst. Professor Suggestions for using the Lecture Slides.
Introduction to Databases
Chapter 2 CIS Sungchul Hong
Database Architecture Introduction to Databases. The Nature of Data Un-structured Semi-structured Structured.
CSC271 Database Systems Lecture # 4.
Database Design - Lecture 2
Midterm Exam Chapters 1,2,3,5, 6,7 (closed book) March 11, 2014.
Database Organization and Design
Ihr Logo Fundamentals of Database Systems Fourth Edition El Masri & Navathe Chapter 2 Database System Concepts and Architecture.
1 Chapter 1 Introduction. 2 Introduction n Definition A database management system (DBMS) is a general-purpose software system that facilitates the process.
1 Chapter 2 Data Model Database Systems: Design, Implementation, and Management, Sixth Edition, Rob and Coronel.
HND Agri DBMS Introduction MH Mohamed Nafas 1. Why DBMS? 2  Suppose we need to develop a Information system.  How do we  store the data? (use file.
Chapter 1 Introduction Yonsei University 1 st Semester, 2015 Sanghyun Park.
1 CS 430 Database Theory Winter 2005 Lecture 2: General Concepts.
Database Environment Chapter 2. Data Independence Sometimes the way data are physically organized depends on the requirements of the application. Result:
The University of Akron Dept of Business Technology Computer Information Systems The Relational Model: Concepts 2440: 180 Database Concepts Instructor:
CIS/SUSL1 Fundamentals of DBMS S.V. Priyan Head/Department of Computing & Information Systems.
Chapter 1 Introduction Yonsei University 1 st Semester, 2014 Sanghyun Park.
Introduction HNDIT DBMS 1. Database Management Systems Module code HNDIT Module title Database Management Systems Credits2HoursLectures15.
2/20: Ch. 6 Data Management What is data? How is it stored? –Traditional management storage techniques; problems –DBMS.
1 Geog 357: Data models and DBMS. Geographic Decision Making.
Chapter 2 Database Environment.
ASET 1 Amity School of Engineering & Technology B. Tech. (CSE/IT), III Semester Database Management Systems Jitendra Rajpurohit.
Chapter 1: Introduction. 1.2 Database Management System (DBMS) DBMS contains information about a particular enterprise Collection of interrelated data.
Database Environment Chapter 2. The Three-Level ANSI-SPARC Architecture External Level Conceptual Level Internal Level Physical Data.
Databases Salihu Ibrahim Dasuki (PhD) CSC102 INTRODUCTION TO COMPUTER SCIENCE.
Data Models. 2 The Importance of Data Models Data models –Relatively simple representations, usually graphical, of complex real-world data structures.
Postgraduate Module Enterprise Database Systems Technological Educational Institution of Larisa in collaboration with Staffordshire University Larisa
©Silberschatz, Korth and Sudarshan 1.1 Database System Concepts قواعد البيانات Data Base قواعد البيانات CCS 402 Mr. Nedal hayajneh E- mail
Introduction: Databases and Database Systems Lecture # 1 June 19,2012 National University of Computer and Emerging Sciences.
Database System Concepts, 5th Ed. ©Silberschatz, Korth and Sudarshan See for conditions on re-usewww.db-book.com Chapter 1: Introduction.
Databases and DBMSs Todd S. Bacastow January 2005.
CS4222 Principles of Database System
Datab ase Systems Week 1 by Zohaib Jan.
Database Management System
Introduction to Database Management System
Data, Databases, and DBMSs
Database.
File Systems and Databases
Data Model.
Chapter 1: Introduction
Object-Oriented Databases
What Goes Around Comes Around
Presentation transcript:

Chapter 1: Data Models and DBMS Architecture Title: What Goes Around Comes Around Authors: M. Stonebraker, J. Hellerstein Pages: 2-40

What Goes Around Comes Around Problem –Problem Statement –Why is this problem important? –Why is this problem hard? Approaches –Approach description, key concepts –Contributions (novelty, improved) –Weaknesses

Problem Statement – Data Model Data Model : wikipedia entrywikipedia entry Given –A set of application domains –Data representation needs, e.g. query, integrity, manipulation Find –A representation language –A set of building-blocks Objectives –Expressiveness –Convenience, i.e. reduce semantic gap (given, find) Constraints –Usability –Performance

Why is this problem important? Common data model yields benefits –Informed decision making Strategies based on corporate-wide information Example: Customer relationship management –Operational efficiencies Inter/Intra-organization communication –Example: Supply chain management Reduced cost of collaboration –Scientific problem solving – Genome sequencing Lack of common data model leads to –Makes data sharing difficult Redundant and inconsistent data across applications –Hampers informed decision making, collaborations, communication, …

Why is this problem Hard? Changes –Set of applications evolve Business data processing (1960s) – COBOL Scientific Apps, Software development (1980s) - Objects Web (1990s) - XML Sensor networks (2000s) … –Platforms evolve Computer Hardware, Languages, Operating Systems Storage: Tapes  Disks (1960s)  RAID (1990s)  SAN … CPUs: Mainframe  Mini  Desktops  Multi-core CPUs (2000s) …

Approaches Nine waves –IMS – Hierarchical Model –CODASYL – Network Model –Relational –Entity Relationship –Relational++ –Semantic Data Model –OO –Object Relational –Semi-structured Approaches –Approach description, key concepts –Contributions (novelty, improved) –Weaknesses

Approaches IMS – Hierarchical Model –Constructs – record types, key, tree –Concepts – physical data independence, logical data independence –Limitations – Many to many binary relationships => duplicates CODASYL – Network Model –Constructs – record types, keys, “set” type (edge), owner, child, network, entry –Limitations – 3-way relationship, lack of physical data independence, bulk load Relational –Constructs – relations, relational algebra, functional dependency –Limitations – transitive closure Entity Relationship –Constructs – entity, relationship, attribute –Limitations – lack of query language

Approaches Relational++ –Constructs- Set-valued attributes, aggregation (tuple reference), generalization Semantic Data Model –Constructs: class, class variable, multiple inheritance, OO –Construct- persistent programming language, no semantic gap, swizzle –Weak support for transactions, queries Object Relational –Constructs: user defined data types, operators, functions and access methods Semi-structured –Concepts: Schema last, Complex network oriented data model –Constructs: DTD, XMLSchema, union types, Xpath

Lessons IMS – Hierarchical Model –1. Physical and logical data independence are desirable –2. Tree structure data models are very restrictive –3. Tree structured data => hard logical reorganization –4. Record-at-a-time interface forces manual query optimization CODASYL – Network Model –5. Networks are more flexible and more complex than trees –6. Loading and recovering networks is more complex than trees Relational –7. Set-a-time language provide improved physical data independence –8. Logical data independence is easier with a simpler data model –9. Technical debates are usually settled by marketplace –10. Query optimizers can beat record-at-a-time programs

Lessons Entity Relationship –11. Functional dependencies are difficult to understand. Relational++ –12. Without big performance or functionality advantages, new construct will go nowhere. Semantic Data Model OO –13. Packages will not sell to users without “major pain” –14. Persistent languages will not succeed w/o help from programming language community Object Relational –15. Putting code in DBMS, user-defined access methods –16. Wide-spread adoption = f (standard, market forces) Semi-structured –17. Schema-last is probably a niche market –18. XQuery = OR SQL with different syntax –19. Semantic heterogeneity >> XML

Lessons IMS – Hierarchical Model –1. Physical and logical data independence are desirable –2. Tree structure data models are very restrictive –3. Tree structured data => hard logical reorganization –4. Record-at-a-time interface forces manual query optimization CODASYL – Network Model –5. Networks are more flexible and more complex than trees –6. Loading and recovering networks is more complex than trees Relational –7. Set-a-time language provide improved physical data independence –8. Logical data independence is easier with a simpler data model –9. Technical debates are usually settled by marketplace –10. Query optimizers can beat record-at-a-time programs Entity Relationship Relational++ Semantic Data Model OO Object Relational Semi-structured