2. B. Information Technology (Hons.) CMPB245: Database Design Physical Design

3. 2 Objectives Explain the purpose of physical database design Design base relations and integrity rules Select an appropriate file organization based on analysis of transactions

4. Physical Database Design: The Purpose Objective 1

5. Databasedesign Implementation Data loading & conversion Physicaldesign Testing Operationalmaintenance Database planning Conceptualdesign Logicaldesign Systemsdefinition Requirements collection & analysis Prototyping DBMSselection

6. 5 Introduction What did we do in Logical Database design? We produced the Conceptual Data Model followed by the Local Logical Data Model and then the Global Logical Data Model What does this global logical data model represents?

7. 6 Introduction Physical database design depends on the functions and power of selected DBMS – More than one way of implementing it At this stage, the task is to – convert the global logical data model into a specific database implementation

8. 7 Physical Database Design What is Physical Database Design? – The process of producing a description of the implementation of the database on secondary storage – It describes the storage structures and access methods used to gain access effectively

9. 8 Physical Database Design It involves the following tasks: – designing the base relations and integrity constraints – selecting specific storage structures and access methods for the data to achieve good performance – designing security measures required on the data

10. 9 Physical Database Design Connolly says that a physical database designer should – know how the computer system hosting the DBMS functions – be fully aware of the functionality of the selected DBMS Physical database design must be tailored to a specific DBMS system

11. 10 Physical Database Design The Tasks Involved 4.0Translate global logical data model for target DBMS 4.1Design base relations for the target DBMS 4.2Design enterprise constraints for the target DBMS

12. 11 Physical Database Design The Tasks Involved 5.0Design and implement physical representation 5.1Analyse transactions 5.2Choose file organizations 5.3Choose secondary indexes 5.4Consider the use of controlled redundancy 5.5Estimate disk space

13. 12 Physical Database Design The Tasks Involved 6.0Design and implement security mechanisms 6.1Design and implement user views 6.2Design and implement access rules 7.0Monitor and tune the operational system

14. Design Base Relations & Integrity Rules Objective 2

15. 14 4.0Translate Global Logical Data Model Translate the relations from the global logical data model into a form that can be implemented in the DBMS – collate the information gathered during logical data modeling and documented in the data dictionary – use this information to produce the design of the base relations

16. 15 4.0Translate Global Logical Data Model Knowledge about the target DBMS the designer should know: – does the system supports the definition of primary, foreign and alternate keys? – does it supports the definition of the required data, e.g. NOT NULL for primary key? – does it supports the definition of domains? – how to create the base relations?

17. 16 4.1Design base relations Required information from the global data model: – the name of the relation – a list of attributes – the primary key, alternate keys and foreign keys – integrity constraints for foreign keys

18. 17 4.1Design base relations For each attribute, you should have: – its domain - data types, length and any constraints – optional default value for the attribute – whether it can hold nulls – whether it is derived and how it is computed

19. 18 4.1Design base relations To represent the design of base relations, use the DDL to define: – domains – default values – null indicators See Fig. 9.1, pg. 273

20. 19 4.1Design base relations Implementation of the base relations depends on the target DBMS Use SQL statements – See Fig. 9.2, pg. 274 – These operations creates the domains, table and constraints Document the design of base relations

21. 20 4.2Design enterprise constraints If an organisation has its own rules governing its real world transactions – Enforce those rules in the target DBMS This depends on the DBMS – Some systems do not support some or all of the enterprise constraints

22. 21 CONSTRAINTS staff_not_handling_too_much CHECK (NOT EXISTS(SELECT sno FROM property_for_rent GROUP BY sno HAVING COUNT(*)>10)) Document the design of enterprise constraintsDocument the design of enterprise constraints 4.2Design enterprise constraints For example, DreamHome would not allow a staff handles more than 10 properties, could be enforced in SQL as follows:

23. Transactions Analysis and File Organization Objective 3

24. 23 5.0Design and implement physical representation At this stage, determine the file organizations and access methods that will be used to store the base relations Efficient file storage can be measured – Transaction throughput - no. of transactions processed in a given time – Response time - elasped time for a single transaction – Disk storage - amount of disk space used

25. 24 5.0Design and implement physical representation The types of file organization depends on the support of the DBMS The designer should fully understand – the storage structures that are available – how the system uses these structures

26. 25 5.0Design and implement physical representation The activities in this stage are: 5.1Analyse transactions 5.2Choose file organizations 5.3Add secondary indexes 5.4Consider the introduction of controlled redundancy 5.5Estimate disk space

27. 26 5.1Analyse transactions Identify the transactions or queries that will run on the database – Why? To determine – the best access structures for the attributes – which type of file is best used

28. 27 5.1Analyse transactions For each transaction, determine: – expected running frequency of transactions, e.g. no. of updates per day – the relations and attributes accessed by the transaction – the type of access – whether query, insert, update, or delete

29. 28 5.1Analyse transactions For update transaction, note the attributes that are updated These may be candidates for avoiding an access structure, e.g. secondary index

30. 29 5.1Analyse transactions For each transaction, determine the attributes use in any predicates – check whether the predicate involves pattern matching range searches exact-match key retrieval These attributes may be candidates for access structures

31. 30 5.1Analyse transactions For each transaction, determine – the attributes of a query that are involved in the join of two or more relations These attributes may be candidates for access structures

32. 31 5.1Analyse transactions For each transaction, determine – time constraints imposed on the transactions, e.g., the transaction must complete within 1 sec Attributes used in any predicates for critical transaction should have a higher priority for access structures

33. 32 5.1Analyse transactions Transaction Usage Map Impossible to analyse all transactions – Investigate the most important ones Use Transaction Usage Map to – identify which relations each transaction accesses – indicate which of these relations are potentially heavily used

34. 33 5.1Analyse transactions Transaction Usage Map Map all transaction paths to relations Determine which relations are most frequently accessed by transactions Analyse selected transactions that involve these relations How to do it? Map all transaction paths to relations Determine which relations are most frequently accessed by transactions Analyse selected transactions that involve these relations How to do it?

35. 34 5.1Analyse transactions Transaction Usage Map Identify transactions, e.g., (A)Insert details for a new member of staff, given branch address (B)List rental properties handled by each staff at a given branch address (C)Assign a rental property to a staff, checking that a staff does not manage more than 10 properties (D)List rental properties handled by each branch office Identify transactions, e.g., (A)Insert details for a new member of staff, given branch address (B)List rental properties handled by each staff at a given branch address (C)Assign a rental property to a staff, checking that a staff does not manage more than 10 properties (D)List rental properties handled by each branch office

36. 35 5.1Analyse transactions Transaction Usage Map Focus on the ER model for the transactions Estimate the average and maximum number of occurrences in each relationships Identify the relations that are most often required Focus on the ER model for the transactions Estimate the average and maximum number of occurrences in each relationships Identify the relations that are most often required

37. 36 5.1Analyse transactions Transaction Usage Map ISAllocated Oversees Has M M M M M M 1 1 1 1 1 1 Staff 1500 Property for Rent Property for Rent 12000 Branch 50 avg = 6 max = 10 avg = 6 max = 10 avg = 50 max = 300 avg = 50 max = 300 avg = 20 max = 40 avg = 20 max = 40 Staff and Property for Rent are accessed more often

38. 37 5.1Analyse transactions Transaction Usage Map Consider the day and time that a transaction is run - peak, average, or min. load Identify the pattern of operation of tran- sactions – mutually exclusive – conflict Examine transactions closely if pattern of operation conflicts Consider the day and time that a transaction is run - peak, average, or min. load Identify the pattern of operation of tran- sactions – mutually exclusive – conflict Examine transactions closely if pattern of operation conflicts

39. 38 5.1Analyse transactions Transaction Usage Map Look how each relation is accessed – Insert (I) – Read (R) – Update (U) – Delete (D) Identify which attributes are used to gain access Asterisk all transactions that scan through a set of records Look how each relation is accessed – Insert (I) – Read (R) – Update (U) – Delete (D) Identify which attributes are used to gain access Asterisk all transactions that scan through a set of records

40. 39 (R)B 5.1Analyse transactions Transaction Usage Map ISAllocated Oversees Has Property for Rent 12000 Staff 1500 B (R) A(I) Branch 50B(R)A(R) (A) Insert details for a new member of staff, given branch address (B) List rental properties handled by each staff at a given branch address

41. 40C(U) 5.1Analyse transactions Transaction Usage Map ISAllocated Oversees Has Property for Rent 12000 C (R) Staff 1500(R)C (R)D Branch 50 D (R) (D) List rental properties handled by each branch office (C) Assign a rental property to a staff, checking that a staff does not manage more than 10 properties

42. 41 5.1Analyse transactions Transaction Table Transaction B DayTimeNumber of runs per hour PeakMon9-10 pm2 Wed2-4 pm2 Ave--- From relationTo relationAttributesAccessNo. of times accessed -Branch1 AddressR(E) BnoR BranchStaff8-20 BnoR(E)* SnoR FNameR LNameR StaffProperty48-200 for RentSnoR(E)* PnoR AddressR Entrypoint A set of records is scanned (B) List rental properties handled by each staff at a given branch address

43. 42 5.0Design and implement physical representation The activities in this stage are: 5.1Analyse transactions 5.2Choose file organizations 5.3Add secondary indexes 5.4Consider the introduction of control-led redundancy 5.5Estimate disk space

44. 43 5.2Choose file organizations Consider using the following file organizations – Heap – Hash – Index Sequential Access Method (ISAM) – B + - Tree

45. 44 5.2Choose file organizations Document choice of file organization Give reasons for your choice based on the advantages of a particular file organization

46. THE END College of Information Technology