1. CSC443 Database Management Course Introduction Professor Pepper adapted from presentations given by Professor Juliana Freire & Karl Aberer & Yan Chen & Silberschatz, Korth and Sudarshan

2. Today’s Goals Course Overview  Why study databases?  Why use databases?  Intro to Databases

3. Major Course Objectives  Design and diagram relational databases  Create Access and Oracle databases  Use SQL commands  Be able to design a good relational database  Know how to get information out of a database to answer any question

4. Diagramming §Use Case §Class Diagram §Entity Relationship Diagram §Algebraic Relation Model

5. Tools §Panther l Unix l Oracle 9.2.0.1.0 §FTP Explorer – register for trial §MS Access

6. Books §Database System Concepts 5 th Ed l Theory l Cross Reference for fourth ed §Oracle 9i Programming - A Primer l Practical examples §See course syllabus §Available in Library

7. Learning Resources §Blackboard: my.adelphi.edumy.adelphi.edu §Web site Database System Concepts: l www.db-book.com/ www.db-book.com/ §My office hours: l Tuesday & Thursday 12:15-1:30; Wed 12- 12:30 l Alumni 114 or Science Lab §My email: pepper@adelphi.edu §My phone: 516-747-2362 §My Web: www.adelphi.edu/~pepperkwww.adelphi.edu/~pepperk

8. Adelphi Account Setup §Panther §Oracle §Blackboard §E-mail §Signin Sheet

9. Projects / Grading §Projects: 40% l Access – 15 l Oracle - 25 §Homework assignments: 20% §Midterm: 20% §Final: 20%.

10. Assignments §2% dropped for anything 1 day late. §10% dropped for anything 2 weeks late.

11. Delivering assignments §Email §ftp §drop box §discussion board §mailbox in math department §E-mail me if making a change in delivery place. §forward your email from Adelphi

12. What is a Database Management System? Database Management System = DBMS §A collection of files that store the data §A big program written by someone else that accesses and updates those files for you Relational DBMS = RDBMS §Data files are structured as relations (tables)

13. Why Study Databases?

14. What is behind this Web Site? §http://www.ticketmaster.com/http://www.ticketmaster.com/ §Search on a large database §Specify search conditions §Many users §Updates §Access through a web interface Central to Modern Computer Science

15. Database Systems: Then

16. Database Systems: Today From Friendster.com on-line tour Field is developing quickly

17. Other databases you may use Databases are EVERYWHERE

18. Current Commercial Outlook §A major part of the software industry: l Oracle, IBM, Microsoft, Sybase l also Informix (now IBM), Teradata l smaller players: java-based dbms, devices, OO, … §Well-known benchmarks (esp. TPC) §Lots of related industries l data warehouse, document management, storage, backup, reporting, business intelligence, app integration §Relational products dominant and evolving l adapting for extensibility (user-defined types), adding native XML support. §Open Source coming on strong l MySQL, PostgreSQL, BerkeleyDB

19. Why Study Databases?? §Need exploded l Corporate: retail swipe/clickstreams, “customer relationship mgmt”, “supply chain mgmt”, “data warehouses”, etc. l Scientific: digital libraries, Human Genome project, NASA Mission to Planet Earth, physical sensors, grid physics network ?

20. Why study databases?  Data is valuable:  bank account records, tax records, student records…  Protect It! - no matter what Hurricane Flood Human error

21. Why study databases? Data often structured:  Example: Bank account records all follow the same structure  We can exploit this regular structure To retrieve data in useful ways (that is, we can use a query language) To store data efficiently

22. Why Study Databases Summary §Central to modern computer science §Databases are everywhere §Commercially successful §Fast moving technology §Plethora of structured data that business and people need

23. What is a database? §Whiteboard Exercise

24. Database Definition §Database l – a very large, integrated collection of data. (the stuff) §Models a real-world enterprise l Entities (e.g., teams, games) l Relationships (e.g., The Forty-Niners are playing in The Superbowl) §Database Management System l – software that stores and manages databases (the tools)

25. Database is better than simple file system because: §Data redundancy, inconsistency and isolation §Difficult to access §Integrity problems §Atomicity of updates (change one file and die before the other completes) §Multiple user issues

26. So a Database Has: §representing information l data modeling §languages and systems for querying data l complex queries with real semantics* l over massive data sets §concurrency control for data manipulation l controlling concurrent access l ensuring transactional semantics §reliable data storage l maintain data semantics even if you pull the plug * semantics: the meaning or relationship of meanings of a sign or set of signs

27. Why Use a Database §Why use a database presentationWhy use a database presentation

28. What is in a database?

29. Describing Data: Data Models §A data model is a collection of concepts for describing data. §A schema is a description of a particular collection of data, using a given data model. §A relation is the data stored in a certain schema §The relational model of data is the most widely used model today. l Entities and relations among them l Integrity constraints and business rules l Perspective dependent (warehouse & sales view item differently)

30. Database Design The process of designing the general structure of the database: §Logical Design – Deciding on the database schema. l Business decision – What attributes l Computer Science decision – What relation schemas §Physical Design – Deciding on the physical layout of the database

31. Data Models §A collection of tools for describing l Data l Data relationships l Data semantics l Data constraints §Relational model §Entity-Relationship data model (mainly for database design) §Object-based data models (Object-oriented and Object-relational) §Semistructured data model (XML) §Other older models: l Network model l Hierarchical model

33. The Entity-Relationship Model §Models an enterprise as a collection of entities and relationships l Entity: a “thing” or “object” in the enterprise that is distinguishable from other objects Described by a set of attributes l Relationship: an association among several entities §Represented diagrammatically by an entity-relationship diagram:

34. Relational Model §ER for concept  map to Algebraic Relational Model §Relations (tables of possible data) §Instance (actual data at a given time) §Schema (description of those tables, their relations)

35. Relational Model Terminology

36. Relational Model Look §Notation:  p (r) §p is called the selection predicate §Defined as:  p (r) = {t | t  r and p(t)} Where p is a formula in propositional calculus consisting of terms connected by :  (and),  (or),  (not) Each term is one of: op or where op is one of: =, , >, . <.  §Example of selection:  branch_name=“Perryridge” (account)

37. Object-Relational Data Models §Extend the relational data model by including object orientation and constructs to deal with added data types. §Allow attributes of tuples to have complex types, including non-atomic values such as nested relations. §Preserve relational foundations, in particular the declarative access to data, while extending modeling power. §Provide upward compatibility with existing relational languages.

38. Design Goals  Design Goals:  Avoid redundant data  Ensure that relationships among attributes represented  Ensure constraints are properly modeled: updates  check for violation of database integrity constraints.

39. Bad Design

40. Queries §What the programmer sees

41. Some Basic SQL Commands §Select – Get rows of data §* - everything §From – the name of the table (relation) will follow §Where – Only get the stuff that matches §Example: Select * from movies where theater = Loews §Exercise – l Write down the query to select all of your friends that live in NY State

42. Example: University Database §Conceptual schema: l Students(sid: string, name: string, login: string, age: integer, gpa:real) l Courses(cid: string, cname:string, credits:integer) l Enrolled(sid:string, cid:string, grade:string) §External Schema (View): l Course_info(cid:string,enrollment:cid:string,enrollment integer) §Physical schema: l Relations stored as unordered files. l Index on first column of Students. l Key to good performance Physical Schema Conceptual Schema View 1View 2View 3 DB

43. Data Independence (levels of abstraction) §Applications insulated from how data is structured and stored. §Logical data independence: Protection from changes in logical structure of data – stablize views. §Physical data independence: Protection from changes in physical structure of data. §Q: Why are these particularly important for DBMS? Physical Schema Conceptual Schema View 1View 2View 3 DB

44. Queries §Change and get data from a database §Run over data model §Easy & efficient §Not good for complex calculations §DML and DDL

45. Data Manipulation Language (DML) §Language for accessing and manipulating the data organized by the appropriate data model l DML also known as query language §Two classes of languages l Procedural – user specifies what data is required and how to get those data l Declarative (nonprocedural) – user specifies what data is required without specifying how to get those data §SQL is the most widely used query language

46. Data Definition Language (DDL) §Specification notation for defining the database schema Example:create table account ( account-number char(10), balance integer) §DDL compiler generates a set of tables stored in a data dictionary §Data dictionary contains metadata (i.e., data about data) l Database schema l Data storage and definition language Specifies the storage structure and access methods used l Integrity constraints Domain constraints Referential integrity (references constraint in SQL) Assertions l Authorization

47. Queries - What does it look like? §System handles query plan generation & optimization; ensures correct execution. SELECT eid, ename, title FROM Emp E WHERE E.sal > $50K SELECT E.loc, AVG(E.sal) FROM Emp E GROUP BY E.loc HAVING Count(*) > 5 SELECT COUNT DISTINCT (E.eid) FROM Emp E, Proj P, Asgn A WHERE E.eid = A.eid AND P.pid = A.pid AND E.loc <> P.loc §Issues: view reconciliation, operator ordering, physical operator choice, memory management, access path (index) use, … EmployeesProjectsAssignments Emp Select  Emp Group(agg) HavingEmp Count distinct  Asgn Join Join Proj

48. SQL §SQL: widely used non-procedural language l Example: Find the name of the customer with customer-id 192-83-7465 selectcustomer.customer_name fromcustomer wherecustomer.customer_id = ‘192-83-7465’ l Example: Find the balances of all accounts held by the customer with customer-id 192-83-7465 selectaccount.balance from depositor, account where depositor.customer_id = ‘192-83-7465’ and depositor.account_number = account.account_number §Application programs generally access databases through one of l Language extensions to allow embedded SQL l Application program interface (e.g., ODBC/JDBC) which allow SQL queries to be sent to a database §For us: Oracle and Access SQL languages

49. A Look underneath

50. Concurrency Control §Concurrent execution of user programs: key to good DBMS performance. l Disk accesses frequent, pretty slow l Keep the CPU working on several programs concurrently. §Interleaving actions of different programs: trouble! l e.g., account-transfer & print statement at same time §DBMS ensures such problems don’t arise. l Users/programmers can pretend they are using a single- user system. (called “Isolation”) l Thank goodness! Don’t have to program “very, very carefully”.

51. Transactions: ACID Properties §Key concept is a transaction: a sequence of database actions (reads/writes). §DBMS ensures atomicity (all-or-nothing property) even if system crashes in the middle. §Each transaction, executed completely, must take the DB between consistent states or must not run at all. §DBMS ensures that concurrent transactions appear to run in isolation. §DBMS ensures durability of committed Xacts even if system crashes. §DBMS can enforce simple integrity constraints on the data.

52. Ensuring Transaction Properites §DBMS ensures atomicity (all-or-nothing property) even if system crashes in the middle of a Xact. §DBMS ensures durability of committed Xacts even if system crashes. §Idea: Keep a log (history) of all actions carried out by the DBMS while executing a set of Xacts: l Before a change is made to the database, the corresponding log entry is forced to a safe location. l After a crash, the effects of partially executed transactions are undone using the log. Effects of committed transactions are redone using the log. l trickier than it sounds!

53. The Log §The following actions are recorded in the log: l Ti writes an object: the old value and the new value. Log record must go to disk before the changed page! l Ti commits/aborts: a log record indicating this action. §Log is often duplexed and archived on “stable” storage. §All log related activities (and in fact, all concurrency control related activities such as lock/unlock, dealing with deadlocks etc.) are handled transparently by the DBMS.

54. Structure of a DBMS §A typical DBMS has a layered architecture. §The figure does not show the concurrency control and recovery components. §Each database system has its own variations. Query Optimization and Execution Relational Operators Files and Access Methods Buffer Management Disk Space Management DB These layers must consider concurrency control and recovery

55. Overall System Structure

56. …must understand how a DBMS works Databases make these folks happy... §DBMS vendors, programmers $20 million industry l Oracle, IBM, MS, Sybase, … §End users §Business, education, science, … §DB application programmers l Eg smart webmasters l Build web services that run off DBMSs §Database administrators (DBAs) l Design logical/physical schemas l Handle security and authorization l Data availability, crash recovery l Database tuning as needs evolve

57. Summary  What is a database – lots of data organized into entities and schemes with a manager  Why study databases? – common use, needed for programming apps  Why use databases? – all the advantages over flat file systems  Intro to Databases  Logical layer:  Query language, data models, transactions  Physical layer  Actual files with indexes, query processing, concurrency, recovery & logs