1 / 36

Intro to Database Systems and Relational Model

This course provides an introduction to database systems and the relational model. Topics covered include database management systems, SQL, data models, and more.

cathyc
Download Presentation

Intro to Database Systems and Relational Model

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. Intro to Database Systemsand Relational Model George Kollios Boston University (based on the slides by Feifei Li, U of Utah)

  2. About the course – Administrivia • Instructor: • George Kollios, gkollios@cs.bu.edu MCS 104, Tue 12:30-2:00 and Wed 1:00-2:30 • Teaching Fellow: • Xiao Zhou, zhouxiao@bu.edu • Ugrad Lab, 730 Coom Ave, Room 302 Thu 3:15-5:15 and Fri 9:00-11:00 • Home Page: • http://www.cs.bu.edu/fac/gkollios/cs660f19 Check frequently! Syllabus, schedule, assignments, announcements… • Piazza site for discussions, etc • Blackboard from Student link for grades

  3. Textbook RaghuRamakrishnan and JohannesGehrke, "DatabaseManagement Systems", McGraw-Hill, ThirdEdition. 2002.

  4. Grading (Tentative) (Tentative Grading) • Written Homeworks: 15% • Midterm: 20% • Final: 25% • Programming Assignments: 40% • See next

  5. Workload • Set of Projects: • “SimpleDB” projects from MIT/UW • Done individually or in pairs • Java-based implementations of key DBMS functions • 5(or 4) project phases: • Files, Operators, Optimizer, Transactions, Recovery • Some Written Homeworks • Exams – 1 Midterm & 1 Final

  6. Why Study Databases?? Big Data Revolution: “Between the dawn of civilization and 2003, we only created five exabytes of information; now we’re creating that amount every two days.” Eric Schmidt, Google

  7. “Big Data” Buzz

  8. “Big Data” Buzz Source: "Big Data: The Next Frontier for Innovation, Competition and Productivity." US Bureau of Labor Statistics | McKinsley Global Institute Analysis

  9. DB System Landscape https://db-engines.com/en/ranking

  10. What’s a database management system (DBMS)?

  11. What’s a database management system (DBMS)? Application Interface SQL Interpreter Query Evaluator Plan Optimizer Plan Executor Plan Generator Data Access Crash Recovery File & Index Manager Security Manager Buffer Manager Transaction Manager Concurrency Control Database System & Metadata Files Data Files Index Files

  12. Highlights • Why use a DBMS? OS provides RAM and disk • Concurrency • Recovery • Abstraction, Data Independence • Query Languages (declarative language: specify what you want, but not how to do it) • Efficiency (for most tasks) • Security • Data Integrity

  13. Data Models • DBMS models real world • Data Model is the link between user’s view of the world and bits stored in DBMS • Many models exist • We will concentrate on the Relational Model • Students(sid: string, name: string, login: string, age: integer, gpa:real) 1010111101

  14. Why Study the Relational Model? • Most widely used model for structured data. • Vendors: IBM DB2, Microsoft SQL Server, Oracle, MySQL, PostgreSQL, etc. • Have motivated the design of many other data models for structured/semi-structured data. • XML, JSON • Is the basis for understanding many models for unstructured data.

  15. Users ANSI/SPARC Model • Views describe how users see the data. • Conceptual schema defines logical structure • Physical schema describes the files and indexes used. View 1 View 2 View 3 Conceptual Schema Physical Schema DB

  16. Relational Database: Definitions • Relational database:a set of relations. • Relation: made up of 2 parts: • Instance : a table, with rows and columns. • #rows = cardinality • Schema :specifiesname of relation, plus name and type of each column. • E.g. Students(sid: string, name: string, login: string, age: integer, gpa: real) • #fields = degree / arity • type: specify the domain of a field (the set of possible valid values a field may take) • Can think of a relation as a setof rows or tuples. • i.e., all rows are distinct

  17. Example Instance of Students Relation • Cardinality = 3, arity = 5 , all rows distinct • Do all values in each column of a relation instance have to be distinct?

  18. SQL - A language for Relational DBs • SQL: standard language for DBMS, structured query language • Data Definition Language (DDL) • create, modify, delete relations • specify constraints • administer users, security, etc. • Data Manipulation Language (DML) • Specify queries to find tuples that satisfy criteria • add, modify, remove tuples

  19. SQL Overview • CREATE TABLE <name> ( <field> <domain>, … ) • INSERT INTO <name> (<field names>) VALUES (<field values>) • DELETE FROM <name> WHERE <condition> • UPDATE <name> SET <field name> = <value> WHERE <condition> • SELECT <fields> FROM <name> WHERE <condition>

  20. Creating Relations in SQL • Creates the Students relation. • Note: the type (domain) of each field is specified, and enforced by the DBMS • whenever tuples are added or modified. • Another example: the Enrolled table holds information about courses students take. CREATE TABLE Students (sid CHAR(20), name CHAR(20), login CHAR(10), age INTEGER, gpa FLOAT) CREATE TABLE Enrolled (sid CHAR(20), cid CHAR(20), grade CHAR(2))

  21. Adding and Deleting Tuples • Can insert a single tuple using: • Can delete a single (or a set of) tuple(s) using: INSERT INTO Students (sid, name, login, age, gpa) VALUES (‘53688’, ‘Smith’, ‘smith@ee’, 18, 3.2) DELETE FROM Students S WHERE S.name = ‘Smith’ • Powerful variants of these commands are available; more later!

  22. Keys • Keys are a way to associate tuples in different relations • Keys are one form of integrity constraint (IC) Enrolled Students

  23. Primary Keys • A set of fields is a superkey if: • No two distinct tuples can have same values in all key fields • A set of fields is a keyfor a relation if : • It is a superkey • No proper subset of the fields is a superkey • >1 key for a relation? • one of the keys is chosen (by DBA) to be the primary key. • E.g. • sidis a key for Students. • What about name? • The set {sid, gpa} is a superkey.

  24. Primary and Candidate Keys in SQL • Possibly many candidate keys(specified using UNIQUE), one of which is chosen as the primary key. CREATE TABLE Enrolled (sid CHAR(20) cid CHAR(20), grade CHAR(2), PRIMARY KEY (sid,cid)) “For a given student and course, there is a single grade.” vs. “Students can take only one course, and receive a single grade for that course; further, no two students in a course receive the same grade.” CREATE TABLE Enrolled (sid CHAR(20) cid CHAR(20), grade CHAR(2), PRIMARY KEY(sid,cid), UNIQUE (cid, grade))

  25. Foreign Keys • A Foreign Key is a field whose values are keys in another relation (think about them as “pointers”). Enrolled Students

  26. Foreign Keys, Referential Integrity • Foreign key : Set of fields in one relation that is used to `refer’ to a tuple in another relation. • Must correspond to primary key of the second relation. • Like a `logical pointer’. • E.g. sid is a foreign key referring to Students: • Enrolled(sid: string, cid: string, grade: string) • If all foreign key constraints are enforced, referential integrityis achieved (i.e., no dangling references.)

  27. Enrolled Students Foreign Keys in SQL • Only students listed in the Students relation should be allowed to enroll for courses. CREATE TABLE Enrolled (sid CHAR(20), cid CHAR(20), grade CHAR(2), PRIMARY KEY (sid,cid), FOREIGN KEY (sid) REFERENCESStudents )

  28. Integrity Constraints (ICs) • IC: condition that must be true for anyinstance of the database; e.g., domain constraints (i.e., types). • ICs are specified when schema is defined. • ICs are checked when relations are modified. • A legalinstance of a relation is one that satisfies all specified ICs. • DBMS should not allow illegal instances. • If the DBMS checks ICs, stored data is more faithful to real-world meaning. • Avoids data entry errors, too!

  29. Where do ICs Come From? • ICs are based upon the semantics of the real-world that is being described in the database relations. • We can check a database instance to see if an IC is violated, but we can NEVER infer that an IC is true by looking at an instance. • An IC is a statement about all possible instances! • From example, we know name is not a key, but the assertion that sid is a key is given to us. • Key and foreign key ICs are the most common; more general ICs supported too.

  30. Enrolled Students Enforcing Referential Integrity • Remember Students and Enrolled; sid in Enrolled is a foreign key that references Students. • What should be done if an Enrolled tuple with a non-existent student id is inserted? • (Reject it!) • What should be done if a Students tuple is deleted? • Also delete all Enrolled tuples that refer to it. • Disallow deletion of a Students tuple that is referred to. • Set sid in Enrolled tuples that refer to it to a default sid. • (In SQL, also: Set sid in Enrolled tuples that refer to it to a special value null, denoting `unknown’ or `inapplicable’.) • Similar if primary key of Students tuple is updated.

  31. Relational Query Languages • A major strength of the relational model: supports simple, powerful querying of data. • Queries can be written intuitively, and the DBMS is responsible for efficient evaluation. • The key: precise semantics for relational queries. • Allows the optimizer to extensively re-order operations, and still ensure that the answer does not change. • Declarative language: specify what you want, and don’t have to worry about how to get the results (e.g., simply say sort, instead of specifying quicksort vs. mergesort)

  32. The SQL Query Language • The most widely used relational query language. • Current std is SQL2011 • To find all 18 year old students, we can write: SELECT * FROM Students S WHERE S.age=18 To find just names and logins, replace the first line: SELECT S.name, S.login FROM Students S WHERE S.age=18

  33. Querying Multiple Relations • What does the following query compute? SELECT S.name, E.cid FROM Students S, Enrolled E WHERE S.sid=E.sid AND E.grade='A' Enrolled Students we get:

  34. Semantics of a Query • A conceptual evaluation methodfor the previous query: 1. do FROM clause: compute cross-product of Students and Enrolled 2. do WHERE clause: Check conditions, discard tuples that fail 3. do SELECT clause: Delete unwanted fields • Remember, this is conceptual. Actual evaluation will be much more efficient, but must produce the same answers.

  35. Cross-product of Students and Enrolled Instances

  36. Relational Model: Summary • A tabular representation of data. • Simple and intuitive, currently the most widely used • Other models are commonly used too (XML, JSON, key-value pairs) • Integrity constraints can be specified by the DBA, based on application semantics. DBMS checks for violations. • Two important ICs: primary and foreign keys • In addition, we always have domain constraints. • Powerful and natural query languages exist.

More Related