Chapter 9 Database Systems Chapter 9 Database Systems

  • Slides: 60
Download presentation
Chapter 9 Database Systems

Chapter 9 Database Systems

Chapter 9: Database Systems n n n n 9. 1 Database Fundamentals 9. 2

Chapter 9: Database Systems n n n n 9. 1 Database Fundamentals 9. 2 The Relational Model 9. 3 Object-Oriented Databases 9. 4 Maintaining Database Integrity 9. 5 Traditional File Structures 9. 6 Data Mining 9. 7 Social Impact of Database Technology 2

Definition of a Database n n Database = a collection of data that is

Definition of a Database n n Database = a collection of data that is multidimensional, since internal links between its entries make the information accessible from a variety of perspectives Flat File = a traditional one-dimensional file storage system that presents information from a single point of view 3

Figure 9. 1 A file versus a database organization 4

Figure 9. 1 A file versus a database organization 4

Advantages and Drawback Database Advantage—reduce storage space, or data inconsistent Drawback—sensitive data being accessed

Advantages and Drawback Database Advantage—reduce storage space, or data inconsistent Drawback—sensitive data being accessed by unauthorized personnel Different users access to different information in the database 5

Schemas n n Schema = a description of the structure of an entire database,

Schemas n n Schema = a description of the structure of an entire database, used by database software to maintain the database Subschema = a description of only that portion of the database pertinent to a particular user’s needs, used to prevent sensitive data from being accessed by unauthorized personnel 6

Database management systems n n To manage the complexity and provide the flexibility of

Database management systems n n To manage the complexity and provide the flexibility of data organization, layers of abstraction is applied to a database implementation. �� Application software, like web browsers, provides a question-and-answer dialogue or a fill-in-the-blanks form to learn what information is required from users. �� 7

Database management systems n n Database Management System (DBMS) = a software layer that

Database management systems n n Database Management System (DBMS) = a software layer that maintains a database and manipulates it in response to requests from applications Distributed Database = a database stored on multiple machines n n DBMS will mask this organizational detail from its users Data independence = the ability to change the organization of a database without changing the application software that uses it 8

Figure 9. 2 The conceptual layers of a database implementation 9

Figure 9. 2 The conceptual layers of a database implementation 9

Database models n Database model = conceptual view of a database n n Relational

Database models n Database model = conceptual view of a database n n Relational database model Object-oriented database model 10

Relational database model n Relation = a rectangular table n n n Attribute =

Relational database model n Relation = a rectangular table n n n Attribute = a column in the table Tuple = a row in the table Most popular database model is the relational database model(RDB). �� Its structure is very simple: data are stored in rectangular tables, called relations. �� A tuple or record is a row in a relation; attributes are columns in a relation. �� 11

Relational database model n n n The entity “G. Jerry Smith”is stored in the

Relational database model n n n The entity “G. Jerry Smith”is stored in the 3 rd row, with Empl. Id=23 Y 34. �� The design of RDB centers on the designs of relations. (Simple!? )�� How many columns necessary in a relation? (the more, the better? ? )�� More columns specialize each tuple as a specific instance of many more possible, rendering unnecessary repeats(redundancy) across several tuples. �� Deletion of a tuple (row) may jointly delete all accompany information (attributes). 12

Figure 9. 3 A relation containing employee information 13

Figure 9. 3 A relation containing employee information 13

Evaluating a relational design n Avoid multiple concepts within one relation n n Can

Evaluating a relational design n Avoid multiple concepts within one relation n n Can lead to redundant data Deleting a tuple could also delete necessary but unrelated information 14

Figure 9. 4 A relation containing redundancy 15

Figure 9. 4 A relation containing redundancy 15

Improving a relational design n n Partial deletion of a tuple introduces complications. Two

Improving a relational design n n Partial deletion of a tuple introduces complications. Two partially deleted tuples may be the same: say, two F 5’s. 16

Improving a relational design n n Decomposition = dividing the columns of a relation

Improving a relational design n n Decomposition = dividing the columns of a relation into two or more relations, duplicating those columns necessary to maintain relationships The rationale behind the scene is the fact that more than one concept should not be combined into one relation, rather one for each concept. Each distinct entity and every relation can be designed as an individual table. Through Assignment relation, the jobs assigned to an employee are known 17

Improving a relational design n Notably, information must be kept during the decomposition (lossless

Improving a relational design n Notably, information must be kept during the decomposition (lossless decomposition). Lossless or nonloss decomposition = a “correct” decomposition that does not lose any information 18

Figure 9. 5 An employee database consisting of three relations 19

Figure 9. 5 An employee database consisting of three relations 19

Figure 9. 6 Finding the departments in which employee 23 Y 34 has worked

Figure 9. 6 Finding the departments in which employee 23 Y 34 has worked 20

Figure 9. 7 A relation and a proposed decomposition 21

Figure 9. 7 A relation and a proposed decomposition 21

Relational operations n n Relations are sets whose records are all identifiable uniquely(say, by

Relational operations n n Relations are sets whose records are all identifiable uniquely(say, by Empl. Id). �� To access the information kept in relations, some operators are defined: �� Select(σ): sieve out the tuples (rows) with the desirable properties from a relation. choose rows Project(π): sieve out the attributes (columns) in selection from a relation. : choose columns Join: assemble information from two or more relations generate a relation T from two relations R & S whose tuples are concatenated and meet some condition (say, R. aid= S. bid, or R. v> S. u). �� 22

Figure 9. 8 The SELECT operation 23

Figure 9. 8 The SELECT operation 23

Figure 9. 9 The PROJECT operation 24

Figure 9. 9 The PROJECT operation 24

Figure 9. 10 The JOIN operation 25

Figure 9. 10 The JOIN operation 25

Figure 9. 11 Another example of the JOIN operation 26

Figure 9. 11 Another example of the JOIN operation 26

Figure 9. 12 An application of the JOIN operation 27

Figure 9. 12 An application of the JOIN operation 27

An example(three-step process) Obtain a list of all employee ID along with the working

An example(three-step process) Obtain a list of all employee ID along with the working department? NEW 1<- JOIN ASSIGNMENT and JOB where ASSIGNMENT. Job. Id=JOB. Job. Id NEW 2<-SELECT from NEW 1 where ASSIGNMENT. Term. Date= “*” LIST<-PROJECT ASSIGNMENT. Empl. Id, JOB. Dept from NEW 2 28

Structured Query Language (SQL) DBMS supports commands written in SQL (from IBM, ANSI standard).

Structured Query Language (SQL) DBMS supports commands written in SQL (from IBM, ANSI standard). �� A sequence of relational operations may be expressed in a single SQL statement. �� SQL is a declarative language, which emphasizes the description of information(what, not how) to be retrieved in terms of three clauses: �� Select attribute 1 (attribute 2, …)⇐ project on a resultant relation From R (, S, …)⇐ 1: σ& π(2+relations: Join; ) Where R. j. Id= S. w. No(, R. rate< S. ratio, …)⇐ for selection (or join) conditions�� 29

SQL examples(a single statement) Obtain a list of all employee ID along with the

SQL examples(a single statement) Obtain a list of all employee ID along with the working department? select Empl. Id, Dept from ASSIGNMENT, JOB where ASSIGNMENT. Job. Id = JOB. Job. Id and ASSIGNMENT. Term. Data = “*” 30

Structured Query Language (SQL) All the relational operations can be mingled in SQL statements.

Structured Query Language (SQL) All the relational operations can be mingled in SQL statements. �� The query processor & optimizer of DBMS will generate & optimize the query tree --leaf nodes are original relations, --intermediate nodes are operators, --the root node is the final relation for output� 31

Structured Query Language (SQL)(example) Query: list all employee names and their dates of initial

Structured Query Language (SQL)(example) Query: list all employee names and their dates of initial employment. �� Select Employee. Name, Assignment. Start. Date From Employee, Assignment Where Employee. Empl. Id=Assignment. Empl. Id. 32

Structured Query Language (SQL) provides the syntax to define tables, views, indices, and insert/delete/update

Structured Query Language (SQL) provides the syntax to define tables, views, indices, and insert/delete/update tuples in the relations. n operations to manipulate tuples n n Insert update delete select 33

SQL examples Add a tuple to the EMPLOYEE relation containing the values given below:

SQL examples Add a tuple to the EMPLOYEE relation containing the values given below: n insert into EMPLOYEE values (‘ 43212’, ‘Sue A. Burt’, ‘ 33 Fair St. ’, ‘ 444661111’) 34

Structured Query Language (SQL) Deletion of the tuple from EMPLOYEE�� Delete from Employee where

Structured Query Language (SQL) Deletion of the tuple from EMPLOYEE�� Delete from Employee where Name = ‘G. Jerry Smith’� � Update of a tuple with new address�� Update Employee Set Address = ‘ 1812 Mary Ave. ’ Where Name = ‘Joe E. Baker’ 35

Object-oriented databases n Object-oriented database = a database constructed by applying the object-oriented paradigm

Object-oriented databases n Object-oriented database = a database constructed by applying the object-oriented paradigm n n n Each data entity stored as a persistent object Relationships indicated by links between objects DBMS maintains inter-object links 36

Object-oriented databases n Persistent object Created objects in database must be saved after the

Object-oriented databases n Persistent object Created objects in database must be saved after the program terminates. In contrast to normal program execution, created objects are discarded after program terminates. 37

Figure 9. 13 The associations between objects in an object-oriented database 38

Figure 9. 13 The associations between objects in an object-oriented database 38

Advantages of object-oriented databases n n Matches design paradigm of object-oriented applications Intelligence can

Advantages of object-oriented databases n n Matches design paradigm of object-oriented applications Intelligence can be built into attribute handlers n n n Example: names of people Naming details Encapsulating in the objects Can handle exotic data types n Example: multimedia Can store intelligent entities Objects can contain methods n 39

Maintaining database integrity n Transaction = a sequence of operations that must all happen

Maintaining database integrity n Transaction = a sequence of operations that must all happen together n n Example: transferring money between bank accounts Transaction log = non-volatile record of each transaction’s activities, built before the transaction is allowed to happen n n Commit point = point at which transaction has been recorded in log Roll-back = procedure to undo a failed, partially completed transaction 40

Maintaining database integrity (continued) n Simultaneous access problems n n n Incorrect summary problem

Maintaining database integrity (continued) n Simultaneous access problems n n n Incorrect summary problem Lost update problem Locking = preventing others from accessing data being used by a transaction n n Shared lock: used when reading data Exclusive lock: used when altering data 41

Traditional file Structures Sequential files n Sequential file = file whose contents can only

Traditional file Structures Sequential files n Sequential file = file whose contents can only be read in order n n Reader must be able to detect end-of-file (EOF) Data can be stored in logical records, sorted by a key field n Greatly increases the speed of batch updates 42

Figure 9. 16 The structure of a simple employee file implemented as a text

Figure 9. 16 The structure of a simple employee file implemented as a text file 43

Figure 9. 14 A procedure for merging two sequential files 44

Figure 9. 14 A procedure for merging two sequential files 44

Figure 9. 15 Applying the merge algorithm (Letters are used to represent entire records.

Figure 9. 15 Applying the merge algorithm (Letters are used to represent entire records. The particular letter indicates the value of the record’s key field. ) 45

Indexed files n Index = list of (key, location) pairs n n Sorted by

Indexed files n Index = list of (key, location) pairs n n Sorted by key values location = where the record is stored 46

Figure 9. 17 Opening an indexed file 47

Figure 9. 17 Opening an indexed file 47

Hashing n n Each record has a key The master file is divided into

Hashing n n Each record has a key The master file is divided into buckets A hash function computes a bucket number for each key value Each record is stored in the bucket corresponding to the hash of its key 48

Figure 9. 18 Hashing the key field value 25 X 3 Z to one

Figure 9. 18 Hashing the key field value 25 X 3 Z to one of 41 buckets 49

Figure 9. 19 The rudiments of a hashing system 50

Figure 9. 19 The rudiments of a hashing system 50

Collisions in Hashing Clustering—a disapropriate number of keys hasing to the same buckets n

Collisions in Hashing Clustering—a disapropriate number of keys hasing to the same buckets n Collision = when two keys hash to the same bucket n Probability that all first 8 records in empty buckets is less then 0. 5 (41/41)(40/41)(39/41). . (34/41)=. 482 n n n Major problem when table is over 75% full Solution: increase number of buckets and rehash all data 51

Data mining n Data mining = a set of techniques for discovering patterns in

Data mining n Data mining = a set of techniques for discovering patterns in collections of data n n Data warehouse = static data collection to be mined n n Relies heavily on statistical analyses Data cube = data presented from many perspectives to enable mining Raises significant ethical issues when it involves personal information 52

Data mining strategies Class description --identify characteristics of people buying small cars n Class

Data mining strategies Class description --identify characteristics of people buying small cars n Class discrimination --properties distinguish people buying used cars from new ones n Cluster analysis --Grouping(I. e. movie(age 4 -10; 25 -40) n 53

Data mining strategies Association analysis --links between grouping(buying potato chips also buying soda) n

Data mining strategies Association analysis --links between grouping(buying potato chips also buying soda) n Outlier analysis --abnormal data(credit card theft) n Sequential pattern analysis --pattern of behavior over time(economic systems in terms of global warming) n 54

Social impact of database technology n Problems n Massive amounts of personal data are

Social impact of database technology n Problems n Massive amounts of personal data are being collected n n Often without knowledge or meaningful consent of affected people Data merging produces new, more invasive information Errors are widely disseminated(spread) and hard to correct Remedies n n Existing legal remedies largely ineffective Negative publicity may be more effective 55

Figure 9. 2 The conceptual layers of a database implementation DBMS 1. How should

Figure 9. 2 The conceptual layers of a database implementation DBMS 1. How should data be stored on disk? 2. Is there a vacancy on flight 243? user 3. How many times should a user mistype a pswd? Appl. Soft 4. How can the PROJECT operation be implmented? DBMS 56

Collisions in Hashing n n 10 buckets, Probability of at least two of three

Collisions in Hashing n n 10 buckets, Probability of at least two of three arbitrary records hashing into the same buckets? (Assume the hash function gives no bucket priority over the others) The probability of all three records hashing to different locations would be (10/10)(9/10)(8/10)=. 72, so the probability of at least two hashing to the same location would be. 28. If a fourth recordwere added, the chances of at least two hashing to the same location would increase to. 496, and a fifth record would increase this to. 6976. Thus, with the five records, it is more likely for clustering to have occurred than not. 57

Problems n n n n Given the two relations X and Y below X:

Problems n n n n Given the two relations X and Y below X: A B 2 s 5 z C D t 1 r 3 w 2 draw the relation Result that would be produced by the following statements? Temp JOIN X and Y where X. A > Y. D Result PROJECT X. B, Y. C from Temp X. B Y. C s z z z t t r w Y: 58

Problems n n n Translate the following query into a single SQL statement. Temp

Problems n n n Translate the following query into a single SQL statement. Temp SELECT from X where A = B Result PROJECT A, C from Temp select A, C from X where A = B 59

Problems n Given a relation called People whose attributes are Name, Father, and Mother

Problems n Given a relation called People whose attributes are Name, Father, and Mother (containing each person’s name as well as the name of that person’s parents), write an SQL statement to obtain a list of all the children of Nathan. select Name from People where Father = “Nathan” 60