Database Systems Introduction SL01

Transcription

1 Course Organization Informatik für Ökonomen II Fall 2010 Database Systems Introduction SL01 Database Systems (5 weeks, Prof. Dr. M. Böhlen) Software Engineering (5 weeks, Prof. Dr. M. Glinz) Security (3 weeks, Prof. Dr. B. Stiller) Lectures take place in KOH-B-10 Time: Thursday 10:15-12:00 Web page: Podcasts will be available (a few days after the lectures) Assessment: successful completion of final exam Exercises are not considered for grade (but they help you to prepare for the final exam) Exam: , 10:15-12:00 Inf4Oec10, SL01 1/58 M. Böhlen, Exercises Information also available on course web page 5 exercises 2 exercises in database systems (Amr Noureldin) 2 exercises in software engineering (Reinhard Stoiber) 1 exercise in security (Guilherme Machado) Download from web page Hand-in in groups is allowed No online hand-in After lecture hand-in of printed hard copy Inf4Oec10, SL01 2/58 M. Böhlen, ifi@uzh Timetable Date Lecture Exercise (tentative) Michael Böhlen Exercise Michael Böhlen Michael Böhlen Exercise Michael Böhlen Hand-in Exercise Michael Böhlen Exercise Martin Glinz Hand-in Exercise Martin Glinz Exercise Martin Glinz Hand-in Exercise Martin Glinz Exercise Martin Glinz Hand-in Exercise Burkhard Stiller Exercise Burkhard Stiller Hand-in Exercise Burkhard Stiller Questions Inf4Oec10, SL01 3/58 M. Böhlen, ifi@uzh Inf4Oec10, SL01 4/58 M. Böhlen, ifi@uzh

2 Office Hours The Database System Module Take place every week Office hours can be used for questions about lectures and exercises Location: RAI-D-017 Dates Monday 12:15-13:00 (Antonio Kümin) Tuesday 17:15-18:00 (Robert Dewer, Hannes Tresch) Thursday 12:30-13:15 (Francisco de Freitas, Jens Birchler) The textbook is Fundamentals of Database Systems by Elmasri and Navathe. Doing the exercises is crucial for the database part. It is the best preparation for the exam. What is important Understand the main properties of database systems. Being able to be precise about key concepts of database systems. Being able to apply your knowledge on relevant examples. Inf4Oec10, SL01 5/58 M. Böhlen, The Database System Module Inf4Oec10, SL01 6/58 M. Böhlen, 1. Introduction to Database Systems Field, terminology, database system, schema, instance, functionality, architecture chapters 1 and 2 in Elmasri and Navathe, 4th edition 2. Relational algebra The relational model, relational algebra chapter 6 in Elmasri and Navathe, 4th edition 3. SQL Data definition language, data manipulation language chapter 8 in Elmasri and Navathe, 4th edition 4. Entity relationship model The design process, the entity-relationship model, entity-relationship to relational model mapping chapters 3 and 7 in Elmasri and Navathe, 4th edition I hear and forget I learn and remember I do and understand Inf4Oec10, SL01 7/58 M. Böhlen, ifi@uzh Inf4Oec10, SL01 8/58 M. Böhlen, ifi@uzh

3 The Database Field/1 Introduction to Database Systems The database field Database and database users Basic database terminology Main characteristics of the database approach Database languages and interfaces Database system architectures History of database systems Journal Publications ACM Transaction on Database System (TODS) The VLDB Journal (VLDBJ) IEEE Transactions on Knowledge and Data Engineering (TKDE) Information Systems (IS) Conference Publications SIGMOD VLDB ICDE EDBT DBLP Bibliography (Michael Ley, Uni Trier, Germany) DBWorld mailing list Inf4Oec10, SL01 9/58 M. Böhlen, The Database Field/2 Inf4Oec10, SL01 10/58 M. Böhlen, The Database Database Field/3 Commercial Products Oracle DB2 (IBM) Microsoft SQL Server Sybase Ingres Informix PC DBMSs : Paradox, Access, Open Source Products PostgreSQL MySQL MonetDB... We will use MySQL for this course. Inf4Oec10, SL01 11/58 M. Böhlen, ifi@uzh Inf4Oec10, SL01 12/58 M. Böhlen, ifi@uzh

4 Typical Activities of Database People Basic Definitions/1 Data modeling Handling large volumes of complex data Distributed databases Design of migration strategies User interface design Development of algorithms Design of languages New data models and systems XML/semi-structured databases Stream data processing Temporal and spatial databases GIS systems About, data, information, and knowledge: Data are facts that can be recorded: book(lord of the Rings, 3, 10) Information = data + meaning book: title = Lord of the rings, volume nr = 3, price in USD = 10 Knowledge = information + application Inf4Oec10, SL01 13/58 M. Böhlen, ifi@uzh Basic Definitions/2 Inf4Oec10, SL01 14/58 M. Böhlen, ifi@uzh Basic Definitions/3 Mini-world: The part of the real world we are interested in Data: Known facts about the mini-world that can be recorded Database (DB): A collection of related data Database Management System (DBMS): A software package to facilitate the creation/maintenance of databases Database System (DBS): DB + DBMS Meta Data: Information about the structure of the DB. Meta data is organized as a DB itself. Inf4Oec10, SL01 15/58 M. Böhlen, ifi@uzh Inf4Oec10, SL01 16/58 M. Böhlen, ifi@uzh

5 Basic Definitions/4 Database Applications A DBMS provides two kind of languages A data definition language (DDL) for specifying the database schema the database schema is stored in the data dictionary the content of data dictionary is called metadata A data manipulation language (DML) for updating and querying databases, i.e., retrieval of information insertion of new information deletion of information modification of information The standard language for database systems is SQL; Intergalactic data speak [Michael Stonebraker]. SQL offers a DDL and DML. Traditional Applications Numeric and Textual Databases More Recent Applications: Multimedia Databases Geographic Information Systems (GIS) Data Warehouses Real-time and Active Databases Many other applications Examples: Bank (accounts) Stores (inventory, sales) Reservation systems University (students, courses, rooms) online sales (amazon.com) online newspapers (nzz.ch) Inf4Oec10, SL01 17/58 M. Böhlen, ifi@uzh Typical DBMS Functionality/1 Inf4Oec10, SL01 18/58 M. Böhlen, ifi@uzh Typical DBMS Functionality/2 Define a particular database in terms of its data types, structures, and constraints Construct or load the initial database contents on a secondary storage medium Manipulating the database: Retrieval: Querying, generating reports Modification: Insertions, deletions and updates to its content Accessing the database through Web applications Sharing by a set of concurrent users and application programs while, at the same time, keeping all data valid and consistent Other features of DBMSs: Protection or security measures to prevent unauthorized access Active processing to take internal actions on data Presentation and visualization of data Maintaining the database and associated programs over the lifetime of the database application (called database, software, and system maintenance) Inf4Oec10, SL01 19/58 M. Böhlen, ifi@uzh Inf4Oec10, SL01 20/58 M. Böhlen, ifi@uzh

6 Database Users/1 Database users have very different tasks. There are those who use and control the database content, and those who design, develop and maintain database applications. Database administrators: Responsible for authorizing access to the database, for coordinating and monitoring its use, acquiring software and hardware resources, controlling its use and monitoring efficiency of operations. Database Designers: Responsible to define the content, the structure, the constraints, and functions or transactions against the database. They must communicate with the end-users and understand their needs. Database Users/2 End-users: They use the data for queries, reports and some of them update the database content. End-users can be categorized into: Casual: access database occasionally when needed Naïve: they make up a large section of the end-user population. They use previously well-defined functions in the form of canned transactions against the database. Examples are bank-tellers or reservation clerks. Sophisticated: These include business analysts, scientists, engineers, others thoroughly familiar with the system capabilities. Many use tools in the form of software packages that work closely with the stored database. Stand-alone: Mostly maintain personal databases using ready-to-use packaged applications. An example is a tax program user that creates its own internal database or a user that maintains an address book Inf4Oec10, SL01 21/58 M. Böhlen, ifi@uzh Data Models Data Model: A set of concepts to describe the structure of a database, the operations for manipulating these structures, and certain constraints that the database should obey. Data Model Structure and Constraints: Different constructs are used to define the database structure Constructs typically include elements (and their data types) as well as groups of elements (e.g., entity, record, table), and relationships among such groups Constraints specify some restrictions on valid data; these constraints must be enforced at all times Data Model Operations These operations are used for specifying database retrievals and updates by referring to the constructs of the data model. Operations on the data model may include basic model operations (e.g. generic insert, delete, update) and user-defined operations (e.g. compute student gpa, update inventory) Inf4Oec10, SL01 22/58 M. Böhlen, ifi@uzh Categories of Data Models Conceptual (high-level, semantic) data models: Provide concepts that are close to the way many users perceive data. (Also called entity-based or object-based data models.) Physical (low-level, internal) data models: Provide concepts that describe details of how data is stored in the computer. These are usually specified in an ad-hoc manner through DBMS design and administration manuals Implementation (representational) data models: Provide concepts that fall between the above two, used by many commercial DBMS implementations (e.g. relational data models used in many commercial systems). Inf4Oec10, SL01 23/58 M. Böhlen, ifi@uzh Inf4Oec10, SL01 24/58 M. Böhlen, ifi@uzh

7 Database Schema Database Schema: The description of a database. Includes descriptions of the database structure, data types, and the constraints on the database. Schema Diagram: An illustrative display of (most aspects of) a database schema. Schema Construct: A component of the schema or an object within the schema, e.g., STUDENT, COURSE. The database schema changes very infrequently. Schema is also called intension. Example of a Database Schema STUDENT Name StudNr Class Major COURSE CourseName CourseNr CreditHours Department PREREQUISITE CourseNr PrerequisiteNr SECTION SectionID CourseNr Semester Year Instructor GRADE REPORT StudNr SectionId Grade Inf4Oec10, SL01 25/58 M. Böhlen, ifi@uzh Database Instance Database Instance: The actual data stored in a database at a particular moment in time. This includes the collection of all the data in the database. Also called database state (or occurrence or snapshot). The term instance is also applied to individual database components, e.g., record instance, table instance, entity instance Initial Database Instance: Refers to the database instance that is initially loaded into the system. Valid Database Instance: An instance that satisfies the structure and constraints of the database. The database instance changes every time the database is updated. Instance is also called extension. Inf4Oec10, SL01 26/58 M. Böhlen, ifi@uzh Example of a Database Instance COURSE CourseName CourseNr CreditHours Department Intro to Computer Science CS CS Data Structures CS CS Discrete Mathematics MATH MATH Databases CS CS SECTION SectionID CourseNr Semester Year Instructor 85 MATH2410 Fall 04 King 92 CS1310 Fall 04 Anderson 102 CS3320 Spring 05 Knuth 112 MATH2410 Fall 05 Chang 119 CS1310 Fall 05 Anderson 135 CS3380 Fall 05 Stone PREREQUISITE CourseNr PrerequisiteNr CS3380 CS3380 CS3320 CS3320 MATH2410 CS1310 GRADE REPORT StudNr SectionId Grade B C 8 85 A 8 92 A B A Inf4Oec10, SL01 27/58 M. Böhlen, ifi@uzh Inf4Oec10, SL01 28/58 M. Böhlen, ifi@uzh

8 The ANSI/SPARC Three Schema Architecture/1 The ANSI/SPARC Three Schema Architecture/2 Proposed to support DBMS characteristics of: Data independence Multiple views of the data Not explicitly used in commercial DBMS products, but has been useful in explaining database system organization Defines DBMS schemas at three levels: Internal schema at the internal level to describe physical storage structures and access paths (e.g indexes). Typically uses a physical data model. Conceptual schema at the conceptual level to describe the structure and constraints for the whole database for a community of users. Uses a conceptual or an implementation data model. External schemas at the external level to describe the various user views. Usually uses the same data model as the conceptual schema. Mappings among schema levels are needed to transform requests and data. Programs refer to an external schema, and are mapped by the DBMS to the internal schema for execution. Data extracted from the internal DBMS level is reformatted to match the user s external view (e.g., formatting the results of an SQL query for display in a Web page) Inf4Oec10, SL01 29/58 M. Böhlen, ifi@uzh The ANSI/SPARC Three Schema Architecture/3 Inf4Oec10, SL01 30/58 M. Böhlen, ifi@uzh Data Independence Logical Data Independence: The capacity to change the conceptual schema without having to change the external schemas and their associated application programs. Physical Data Independence: The capacity to change the internal schema without having to change the conceptual schema. For example, the internal schema may be changed when certain file structures are reorganized or new indexes are created to improve database performance When a schema at a lower level is changed, only the mappings between this schema and higher-level schemas need to be changed in a DBMS that fully supports data independence. The higher-level schemas themselves are unchanged. Hence, the application programs need not be changed since they refer to the external schemas. Inf4Oec10, SL01 31/58 M. Böhlen, ifi@uzh Inf4Oec10, SL01 32/58 M. Böhlen, ifi@uzh

9 Main Characteristics of Database Approach/1 Main Characteristics of Database Approach/2 Data Abstraction: A data model is used to hide storage details and present the users with a conceptual view of the database. Programs refer to the data model constructs rather than data storage details Support of multiple views of the data: Each user may see a different view of the database, which describes only the data of interest to that user. Self-describing nature of a database system: A DBMS catalog stores the description of a particular database (e.g. data types, data structures, and constraints) The description is called metadata. This allows the DBMS software to work with different database applications. Insulation between programs and data: Called data independence. Allows changing data structures and storage organization without having to change the DBMS access programs. Inf4Oec10, SL01 33/58 M. Böhlen, ifi@uzh Main Characteristics of Database Approach/3 Example of a DBMS catalog (just the idea; oversimplified): RELATIONS RelationName NrOfColumns STUDENT 4 COURSE 4 SECTION 5 GRADE REPORT 3 PRERQUISITE 2 COLUMNS ColumnName DataType BelongsToRelation Name Character(30) STUDENT StudentNr CHARACTER(4) STUDENT Class INTEGER(1) STUDENT Inf4Oec10, SL01 34/58 M. Böhlen, ifi@uzh Main Characteristics of Database Approach/4 Sharing of data and multi-user transaction processing: Allowing a set of concurrent users to retrieve from and to update the database. Concurrency control within the DBMS guarantees that each transaction is correctly executed or aborted Recovery subsystem ensures each completed transaction has its effect permanently recorded in the database OLTP (Online Transaction Processing) is a major part of database applications. This allows hundreds of concurrent transactions to execute per second. PostgreSQL 8.3.9: 74 objects in the system catalog Oracle 10.2: 1821 objects in the system catalog Inf4Oec10, SL01 35/58 M. Böhlen, ifi@uzh Inf4Oec10, SL01 36/58 M. Böhlen, ifi@uzh

10 DBMS Languages/1 DBMS Languages/2 A DBMS offers a data definition language (DDL) and a data manipulation language (DML) We distinguish between High level or declarative languages Low level or procedural languages High level or declarative language: For example, the SQL relational language Are set-oriented and specify what data to retrieve rather than how to retrieve it. Also called non-procedural languages. Low level or procedural language: Retrieve data one record at a time; Constructs such as looping are needed to retrieve multiple records, along with positioning pointers. Data Definition Language (DDL): Used by the DBA and database designers to specify the conceptual schema of a database. In many DBMSs, the DDL is also used to define internal and external schemas (views). In some DBMSs, separate storage definition language (SDL) and view definition language (VDL) are used to define internal and external schemas. SDL is typically realized via DBMS commands provided to the DBA and database designers Inf4Oec10, SL01 37/58 M. Böhlen, ifi@uzh DBMS Languages/3 Inf4Oec10, SL01 38/58 M. Böhlen, ifi@uzh DBMS Interfaces/1 Data Manipulation Language (DML): Used to specify database retrievals and updates DML commands can be embedded in a general-purpose programming language, such as COBOL, C, C++, or Java. A library of functions can also be provided to access the DBMS from a programming language Alternatively, stand-alone DML commands can be issued directly. Stand-alone query language interfaces Example: Entering SQL queries at the DBMS interactive SQL interface (e.g. psql in PostgreSQL, sqlplus in Oracle) Programmer interfaces for embedding DML in programming languages User-friendly interfaces Menu-based, forms-based, graphics-based, etc. Speech as Input and Output Web Browser as an interface Parametric interfaces, e.g., bank tellers using function keys. Interfaces for the DBA: Creating user accounts, granting authorizations Setting system parameters Changing schemas or access paths Inf4Oec10, SL01 39/58 M. Böhlen, ifi@uzh Inf4Oec10, SL01 40/58 M. Böhlen, ifi@uzh

11 DBMS Interfaces/2 Components of the DBS Architecture There are various database system utilities to perform certain functions such as: Loading data stored in files into a database. Includes data conversion tools. Backing up the database periodically on tape. Reorganizing database file structures. Report generation utilities. Performance monitoring utilities. Other functions, such as sorting, user monitoring, data compression, etc. Inf4Oec10, SL01 41/58 M. Böhlen, ifi@uzh 1-tier Architecture/1 Inf4Oec10, SL01 42/58 M. Böhlen, ifi@uzh 1-tier Architecture/2 Centralized DBMS: Combines everything (DBMS software, hardware, application programs, and user interface processing software) into a single system. Users can still connect through a remote terminal All processing is done at a centralized site. DBMS must do everything (e.g., support for interfaces, terminals, connections,...) The DBMS gets huge and cumbersome Inf4Oec10, SL01 43/58 M. Böhlen, ifi@uzh Inf4Oec10, SL01 44/58 M. Böhlen, ifi@uzh

12 2-tier Architecture/1 Specialized Servers with Specialized functions Print server File server DBMS server Web server server Clients can access the specialized servers as needed 2-tier Architecture/2 Clients: Provide appropriate interfaces through a client software module to access and utilize the various server resources. Clients may be diskless machines or PCs or Workstations with disks with only the client software installed. Connected to the servers via some form of a network. (local area network, wireless network, etc.) DBMS Server: Provides database query and transaction services to the clients Relational DBMS servers are often called SQL servers, query servers, or transaction servers Applications running on clients utilize an application program interface (API) to access server databases via standard interfaces: ODBC: Open Database Connectivity standard JDBC: for Java programming access Client and server must install appropriate client module and server module software for ODBC or JDBC Inf4Oec10, SL01 45/58 M. Böhlen, ifi@uzh 3-tier Architecture/1 Inf4Oec10, SL01 46/58 M. Böhlen, ifi@uzh 3-tier Architecture/2 Common for web applications Intermediate layer called application server or web server: Stores the web connectivity software and the business logic part of the application used to access the corresponding data from the database server Acts like a conduit for sending partially processed data between the database server and the client. Three-tier architecture can enhance security: Database server only accessible via middle tier Clients cannot directly access database server Inf4Oec10, SL01 47/58 M. Böhlen, ifi@uzh Inf4Oec10, SL01 48/58 M. Böhlen, ifi@uzh

13 History of Data Models/1 Network Model Hierarchical Model Relational Model Object-oriented Data Models Object-Relational Models History of Data Models/2 Network Model: The first network DBMS was implemented by Honeywell in (IDS System). Adopted heavily due to the support by CODASYL (Conference on Data Systems Languages) (CODASYL - DBTG report of 1971). Advantages: The network model is able to model complex relationships. Can handle most situations for modeling using record types and relationship types. Language is navigational; uses constructs like FIND, FIND member, FIND owner, FIND NEXT within set, GET, etc. Programmers can do optimal navigation through the database. Disadvantages: Navigational and procedural nature of processing Database contains a complex array of pointers that thread through a set of records. Little scope for automated query optimization Inf4Oec10, SL01 49/58 M. Böhlen, ifi@uzh History of Data Models/3 Hierarchical Data Model: Initially implemented in a joint effort by IBM and North American Rockwell around Resulted in the IMS family of systems. IBM s IMS product had (and still has) a very large customer base worldwide Hierarchical model was formalized based on the IMS system Other systems based on this model: System 2k (SAS inc.) Advantages: Simple to construct and operate Corresponds to a number of natural hierarchically organized domains, e.g., organization chart Language is simple; Uses constructs like GET, GET UNIQUE, GET NEXT, GET NEXT WITHIN PARENT, etc. Disadvantages: Navigational and procedural nature of processing Database is visualized as a linear arrangement of records Little scope for query optimization Inf4Oec10, SL01 50/58 M. Böhlen, ifi@uzh History of Data Models/4 Relational Model: Proposed in 1970 by E.F. Codd (IBM) First commercial system in Now in several commercial products (e.g. DB2, ORACLE, MS SQL Server, SYBASE, INFORMIX). Several free open source implementations, e.g. MySQL, PostgreSQL Currently most dominant for developing database applications. SQL relational standards: SQL-89 (SQL1), SQL-92 (SQL2), SQL-99, SQL3,... Inf4Oec10, SL01 51/58 M. Böhlen, ifi@uzh Inf4Oec10, SL01 52/58 M. Böhlen, ifi@uzh

14 History of Data Models/5 Object-oriented Data Models: Several models have been proposed for implementing in a database system. One set comprises models of persistent O-O Programming Languages such as C++ (e.g., in OBJECTSTORE or VERSANT), and Smalltalk (e.g., in GEMSTONE). Additionally, systems like O2, ORION, IRIS (HP). Object Database Standard: ODMG-93, ODMG-version 2.0, ODMG-version 3.0. Object-Relational Models: Most recent trend. Started with Informix Universal Server. Relational systems incorporate concepts from object databases leading to object-relational systems. Exemplified in the latest versions of Oracle-10i, DB2, and SQL Server and other DBMSs. Standards included in SQL-99 and expected to be enhanced in future SQL standards. Advantages of Using a DBMS/1 Controlling redundancy in data storage Restricting unauthorized access to data. Providing persistent storage for program objects Providing storage structures (e.g. indexes) for efficient query processing Providing backup and recovery services. Providing multiple interfaces to different classes of users. Representing complex relationships among data. Enforcing integrity constraints on the database (= good data quality). Drawing inferences and actions from the stored data using deductive and active rules Inf4Oec10, SL01 53/58 M. Böhlen, ifi@uzh Advantages of Using a DBMS/2 Inf4Oec10, SL01 54/58 M. Böhlen, ifi@uzh When to Not Use a DBMS Potential for enforcing standards: This is very crucial for the success of database applications in large organizations. Standards refer to data item names, display formats, screens, report structures, meta-data (description of data), Web page layouts, etc. Reduced application development time: Incremental time to add each new application is reduced. Flexibility to change data structures: Database structure may evolve as new requirements are defined. Availability of current information: Extremely important for on-line transaction systems such as airline, hotel, car reservations. Economies of scale: Wasteful overlap of resources and personnel can be avoided by consolidating data and applications across departments. Main inhibitors of using a DBMS: High initial investment and possible need for additional hardware. Overhead for providing generality, security, concurrency control, recovery, and integrity functions. When a DBMS may be unnecessary: If the database and applications are simple, well defined, and not expected to change. If there are stringent real-time requirements that may not be met because of DBMS overhead. If access to data by multiple users is not required. When no DBMS may suffice: If the database system is not able to handle the complexity of data because of modeling limitations If the database users need special operations not supported by the DBMS. Inf4Oec10, SL01 55/58 M. Böhlen, ifi@uzh Inf4Oec10, SL01 56/58 M. Böhlen, ifi@uzh

15 Summary/1 Companies (start to) use database systems because there is no other solution to manage the data. The data is often by far the biggest asset of a company. Database systems allow to control the redundancy of the data. Database systems provide data independence the access to the data is done logically and never relies on the physical data organization this allows to change the storage organization, update HW, update SW, etc SQL is the standard database query language. Summary/2 Data Models data model = structures + operations + constraints Schemas and Instances schema = intension; changes infrequently relation instance = relation = extension; changes often Three-Schema Architecture external, conceptual, and internal schema Data Independence reorganize internal schema without changing conceptual schema DBMS Languages and Interfaces stand-alone command line interfaces: psql, sqlplus,... programming interfaces: ODBC, JDBC database development tools: pgadmin, SQL developer History of Data Models network, hierarchical, relational, object-oriented, object-relational Inf4Oec10, SL01 57/58 M. Böhlen, ifi@uzh Inf4Oec10, SL01 58/58 M. Böhlen, ifi@uzh