Pertemuan <<8>><<Perancangan Model Fisikal >><<Perancangan Model Fisikal >>

1

Learning Outcomes

Pada akhir pertemuan ini, diharapkan mahasiswa akan mampu :• << TIK-8 >> Mahasiswa dapat

menghasilkan model fisikal databaseberdasarkan suatu model logikal databaseberdasarkan suatu model logikal database(C3)

2

Outline Materi

• Rancangan Basis Relasi• Rancangan Representasi Data• Rancangan Kendala Perusahaan• Analisis Transksi• Analisis Transksi• Pemilihan Organisasi File• Pemilihan Indeks• Estimasi Kebutuhan Disk Space

3

Rancangan Fisikal

Proses produksi untuk menguraikanimplementasi database padasecondary storage; basis relasi,organisasi file, penggunaan indekorganisasi file, penggunaan indekuntuk mengefisienkan access data,penentuan kendala perusahaan dansistem keamanan.

4

Overview of Physical Database Design Methodology

• Step 4 Translate global logical data model for target DBMS– Step 4.1 Design base relations– Step 4.2 Design representation of derived – Step 4.2 Design representation of derived

data – Step 4.3 Design enterprise constraints

5

Overview of Physical Database Design Methodology

• Step 5 Design physical representation– Step 5.1 Analyze transactions– Step 5.2 Choose file organizations– Step 5.2 Choose file organizations– Step 5.3 Choose indexes– Step 5.4 Estimate disk space

requirements

6

Overview of Physical Database Design Methodology

• Step 6 Design user views • Step 7 Design security mechanisms• Step 8 Consider the introduction of

controlled redundancy controlled redundancy • Step 9 Monitor and tune the

operational system

7

Step 4 Translate Global Logical Data Model for Target

DBMSTo produce a relational database schema that can be implemented in the target DBMS from the global logical data model.

• Need to know functionality of target DBMS • Need to know functionality of target DBMS such as how to create base relations and whether the system supports the definition of:– PKs, FKs, and AKs;

– required data – i.e. whether system supports NOT NULL;

– domains;

– relational integrity constraints;

– enterprise constraints. 8

DBDL for the PropertyForRent Relation

9

PropertyforRent Relation and StaffRelation with Derived Attribute

noOfProperties

10

Step 4.3 Design Enterprise Constraints

To design the enterprise constraints for the target DBMS.

• Some DBMS provide more facilities than others for defining enterprise constraints.others for defining enterprise constraints.Example:

CONSTRAINT StaffNotHandlingTooMuchCHECK (NOT EXISTS (SELECT staffNo

FROM PropertyForRent

GROUP BY staffNo

HAVING COUNT(*) > 100))

11

Step 5 Design Physical Representation

To determine optimal file organizations to store the base relations and the indexes that are required to achieve acceptable required to achieve acceptable performance; that is, the way in which relations and tuples will be held on secondary storage.

12

Analisis Transaksi Pada Relasi

13

Transaction Usage Map for Some Sample Transactions Showing

Expected Occurrences

14

Example Transaction Analysis Form

15

Step 5.2 Choose File Organizations

To determine an efficient file organization for each base relation.

• File organizations include Heap, • File organizations include Heap, Hash, Indexed Sequential Access Method (ISAM), B+-Tree, and Clusters.

16

Step 5.3 Choose Indexes

To determine whether adding indexes will improve the performance of the system.

• One approach is to keep tuplesunordered and create as manysecondary indexes as necessary.

17

Step 5.3 Choose Indexes

• Another approach is to order tuplesin the relation by specifying aprimary or clustering index.

• In this case, choose the attribute for• In this case, choose the attribute forordering or clustering the tuples as:– attribute that is used most often for join

operations - this makes join operationmore efficient, or

– attribute that is used most often toaccess the tuples in a relation in orderof that attribute. 18

Step 5.3 Choose Indexes

• If ordering attribute chosen is key ofrelation, index will be a primaryindex; otherwise, index will be aclustering index.clustering index.

• Each relation can only have either aprimary index or a clustering index.

• Secondary indexes provide amechanism for specifying anadditional key for a base relation thatcan be used to retrieve data more

19

Step 5.4 Estimate Disk Space Requirements

To estimate the amount of diskspace that will be required by thedatabase.

20

Step 6 Design User Views

To design the user views that were identified during the Requirements Collection and Analysis stage of the relational database application relational database application lifecycle.

21

Step 7 Design Security Measures

To design the security measures for the database as specified by the users.

22