1 / 30

COMP 530 Database Architecture and Implementation

COMP 530 Database Architecture and Implementation. 1. Introduction. Why Learn DBMS?. You want to find a JOB !!!. Big Names in Database Systems. Web data management. Who Needs Database Systems. Typical Applications: Personnel management Inventory and purchase order

sheena
Download Presentation

COMP 530 Database Architecture and Implementation

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. COMP 530 Database Architecture and Implementation 1. Introduction Department of Computer Science, HKUST Slide 1

  2. Why Learn DBMS? You want to find a JOB !!! Department of Computer Science, HKUST Slide 2

  3. Big Names in Database Systems Department of Computer Science, HKUST Slide 3

  4. Web data management Who Needs Database Systems Typical Applications: Personnel management Inventory and purchase order Insurance policies and customer data … … Corporate databases Typical Applications: Web page management Personalize web pages … … Department of Computer Science, HKUST Slide 4

  5. There is a difference between DBMSs (Database Management Systems) and DatabasesA few people work for Oracle, etc., to develop, enhance or maintain their DBMS productsMost people make a living working as DB designers, DB programmers or DB Administrators Department of Computer Science, HKUST Slide 5

  6. What is in a Database? • A database contains information about a particular enterpriseor a particularapplication. • E.g., a database for an enterprise may contain everything needed for the planning and operation of the enterprise: customer information, employee information, product information, sales and expenses, etc. • You don’t have to be a company to use a database: you can store your personal information, expenses, phone numbers in a database (e.g., using Access on a PC). • As a matter of fact, you could store all data pertinent to a particular purpose in a database. • This usually means that a database stores data that are related to each other. Department of Computer Science, HKUST Slide 6

  7. Database Design HKUST Academic Registration database: students: names, address, … courses: course-no, course-names, … classroom: number, location, … db designer 1 db designer 2 Estate Management database: classroom: number, location, … office: number, location, … faculty-residence: building-no, … student-residence: hall-no, … Department of Computer Science, HKUST Slide 7

  8. Is a database the same as a bunch of files? • You can store data in a file or a set of files, but … • How do you input data and to get back the data from the files? • A database is managed by a DBMS. Department of Computer Science, HKUST Slide 8

  9. Applications Data Files Inventory Control User Customer Order User Before we have DBMS Question: When a customer ordered 10 PC monitors, how many files do you have to update? Key issues: data sharing, data redundancy Department of Computer Science, HKUST Slide 9

  10. SQL DBMS • Shared facilities: • Backup and recovery • Data storage and access modules • Programming tools, etc. C/C++ Programs A Simple Architecture Databases Applications Department of Computer Science, HKUST Slide 10

  11. Purposes of Database Systems Database management systems were developed to handle the difficulties caused by different people writing different applications independently. Department of Computer Science, HKUST Slide 11

  12. Specifically … • A DBMS attempts to resolve the following problems: • Data redundancy and inconsistency by keeping one copy of a data item in the database • Difficulty in accessing data by provided query languages and shared libraries • Data isolation (multiple files and formats) • Integrity problems by enforcing constraints (age > 0) • Atomicity of updates • Concurrent access by multiple users • Security problems Department of Computer Science, HKUST Slide 12

  13. Data Independence • One big problem in application development is the separation of applications from data • Do I have change my program when I … • replace my hard drive? • store the data in a b-tree instead of a hash file? • partition the data into two physical files (or merge two physical files into one)? • store salary as floating point number instead of integer? • develop other applications that use the same set of data? • add more data fields to support other applications? • … … Independence between Data and Programs/Applications Department of Computer Science, HKUST Slide 13

  14. Data Independence • Ability to modify a schema definition in one level without affecting a schema definition in the next higher level. • The interfaces between the various levels and components should be well defined so that changes in some parts do not seriously influence others. • Two levels of data independence: - Physical data independence - Logical data independence Department of Computer Science, HKUST Slide 14

  15. Main Program functions functions data Data Abstraction • The answer to the previous questions is to introduce levels of abstraction of indirection. • Consider how do function calls allow you to change a part of your program without affecting other parts? Department of Computer Science, HKUST Slide 15

  16. Payroll Inventory Sales Company database Files on disks Three Levels of Abstraction view 1 view 2 view n ..……... Logical view Physical view Department of Computer Science, HKUST Slide 16

  17. Application view View definitions logical Logical schema physical Physical schema Department of Computer Science, HKUST Slide 17

  18. Three Levels of Abstraction (cont.) • Physical level: describe how a record is stored on disks. • e.g., “Divide the customer records into 3 partitions and store them on disks 1, 2 and 3.” • Logical level: describes data stored in database, and the relationships among the data. Similar to defining a record type in Pascal or C:Type customer = record name: string; street: string; city: integer; end; • View level: Define a subset of the database for a particular application. Views can also hide information (e.g. salary) for security purposes. Department of Computer Science, HKUST Slide 18

  19. 1129 1129 John Law John Law … … … … An Example of Data Independence Data on disk • Program accessing data directly has to know: • first 4 bytes is an ID number • next 10 bytes is an employee name program Schema Data on disk Employee: ID: integer Name char(10) DBMS program Department of Computer Science, HKUST Slide 19

  20. Instances and Schemas • Each level is defined by a schema, which defines the data at the corresponding level • A logical schema defines the logical structure of the database (e.g., set of customers and accounts and the relationship between them) • A physical schema defines the file formats and locations • A databaseinstance refers to the actual content of the database at a particular point in time. A database instance must conform to the corresponding schema Department of Computer Science, HKUST Slide 20

  21. Data Models • A collection of tools for describing: • data • data relationships • data semantics • data constraints Department of Computer Science, HKUST Slide 21

  22. Entity-Relationship Model • Example of entity-relationship model social-security customer-street balance account-number customer-city customer-name DEPOSITER CUSTOMER ACCOUNT Department of Computer Science, HKUST Slide 22

  23. customer- social- customer- customer- account- name security street city number Johnson 192-83-7465 Alma Palo Alto A-101 Smith 019-28-3746 North Rye A-215 Johnson 192-83-7465 Alma Palo Alto A-201 Jones 321-12-3123 Main Harrison A-217 Smith 019-28-3746 North Rye A-201 account-number balance A-101 500 A-201 900 A-215 700 A-217 750 Relational Model Example of tabular data in the relational model: Department of Computer Science, HKUST Slide 23

  24. Data Definition Language (DDL) • Specification notation for defining the database schema • Express what were in the previous two slides to the DBMS in a formal language • Data storage and definition language - special type of DDL in which the storage structure and access methods used by the database system are specified Department of Computer Science, HKUST Slide 24

  25. Data Manipulation Language (DML) • Language for accessing and manipulation the data organized by the appropriate data model • Two classes of languages • Procedural - user specifies what data is required and how to get those data. • Nonprocedural - user specifies what data is required without specifying how to get those data Department of Computer Science, HKUST Slide 25

  26. Transaction 1 Transaction 1 Transaction 2 Conflicting read/write Transaction Management • A transaction is a collection of operations that performs a single logical • function in database application time Department of Computer Science, HKUST Slide 26

  27. Transaction Management (cont.) • Transaction-management component ensures that the database remains in a consistent (correct) state despite system failures (e.g. power failures and operating system crashes) and transaction failures. • Concurrency-control manager controls the interaction among the concurrent transactions, to ensure the consistency of the database. Department of Computer Science, HKUST Slide 27

  28. Storage Management • A storage manager is a program module that provides the interface between the low-level data stored in the database and the application programs and queries submitted to the system. • The storage manager is responsible for the following tasks: • interaction with the file manager • efficient storing, retrieving, and updating of data. Department of Computer Science, HKUST Slide 28

  29. Database Administrator (DBA) • Coordinates all the activities of the database system; the database administrator has good understanding of the enterprise’s information resources and needs. • Database administrator’s duties include: • Schema definition • Specifying integrity constraints • Storage structure and access method definition • Schema and physical organization modification • Granting user authority to access the database • Acting as liaison with users • Monitoring performance and responding to changes in requirements Primary job of a database designer More system oriented Department of Computer Science, HKUST Slide 29

  30. Database Users • Users are differentiated by the way they expected to interact with the system • Application programmers • Develop applications that interact with DBMS through DML calls • Sophisticated users • form requests in a database query language • mostly one-time ad hoc queries • End users • invoke one of the existing application programs (e.g., print monthly sales report) • Interact with applications through GUI Department of Computer Science, HKUST Slide 30

More Related