1 / 15

Class 4 Agenda

Class 4 Agenda. Database Management Systems Chapter 4: Moore’s Law Midterm Case. Database Management Systems: What?. Software that owns and manages data Two models Relational DBMS Object-oriented DBMS Provides “Storage” layer to applications

rhonda-leach
Download Presentation

Class 4 Agenda

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. Class 4 Agenda • Database Management Systems • Chapter 4: Moore’s Law • Midterm Case

  2. Database Management Systems: What? • Software that owns and manages data • Two models • Relational DBMS • Object-oriented DBMS • Provides “Storage” layer to applications • Can provide logic (constraints) to applications

  3. Database Management Systems: Why? • Insulate users from data mechanics • Ensure business rules are universally applied • Allow simultaneous access • Increase granularity of access • Standardize access language (SQL)

  4. Database Management Systems: Who? • Oracle • Microsoft: SQLServer • IBM: UDB / DB2 • Open Systems: MySQL, PostGres, … • CA, Sybase, …

  5. The DBMS Server layers Application Heavy Client (Sqlplus) App Server Web Server (isqlplus) DBMS Storage DBMS Client DBMS Server Database Tablespace Table Tablespace Table Table Server Instance Schema Instance Schema Schema “Connects” “Mounts”

  6. DBMS Functions • Data Integrity • Accurate and reliable • Access Control • Views • Grants • Multiple levels of access • DataAccess API • Single well-known interface • Single point of control • DBMS Owns the files • Utilities

  7. Data Integrity • Locking • Allows simultaneous use • Different levels available • Constraints • Limits on acceptable entries • Discussed in detail later • Logging • Undoing failed work • Recording completed work

  8. Access Control • Support for users and roles • Granularity for data (Views) • Vertical • Horizontal • Granularity for Function • Read vs change • Procedural access only

  9. SQL API • Defines the access syntax • Open Standard • Extensions for each vendor

  10. Relational DBMS Concepts • Value-based relations • Joins • Tables and Views • Set Processing

  11. Object-Oriented DBMS’s • Purpose: Make storage a service • Classes and Objects • Basic logic joined to data • Object “behavior” • Behavior request mechanism (messages)

  12. Object-Oriented DBMS Concepts • Inheritance • Proper scope for all data, behaviors • Encapsulation • Inner workings hidden from users • Focus on behavior, not process • Polymorphism • Each class can interpret requests

  13. Chapter 4 Comments: Moore’s Law • Reasons for improvement • Caching • Applies to network, storage as well • Tiers of computing need • Parallel processing

  14. Group Reviews: Moore’s Law Pick one, 4 minute response • Impact on “cash cow” phase of product delivery • Impact on purchasing decisions • Is it coming to an end? • Why does network speed come in bigger increments? • The sixth wave? • Where is the most waste?

  15. Midterm Case Introduction: Toyota, The Big Fix • Issues • Project Management • Governance? • Reporting • Assignment • Read • Questions on Wednesday?

More Related