1 Pertemuan > > Matakuliah: >/ > Tahun: > Versi: >
-
Upload
samuel-boddy -
Category
Documents
-
view
243 -
download
1
Transcript of 1 Pertemuan > > Matakuliah: >/ > Tahun: > Versi: >
![Page 1: 1 Pertemuan > > Matakuliah: >/ > Tahun: > Versi: >](https://reader036.fdocuments.net/reader036/viewer/2022081504/56649c815503460f94939a41/html5/thumbnails/1.jpg)
1
Pertemuan <<8>><<Perancangan Model Fisikal >>
Matakuliah : <<T0773>>/<<Perancangan Databasel>>
Tahun : <<2005>>
Versi : <<1/2>>
![Page 2: 1 Pertemuan > > Matakuliah: >/ > Tahun: > Versi: >](https://reader036.fdocuments.net/reader036/viewer/2022081504/56649c815503460f94939a41/html5/thumbnails/2.jpg)
2
Learning Outcomes
Pada akhir pertemuan ini, diharapkan mahasiswa
akan mampu :
• << TIK-8 >> Mahasiswa dapat menghasilkan model fisikal database berdasarkan suatu model logikal database (C3)
![Page 3: 1 Pertemuan > > Matakuliah: >/ > Tahun: > Versi: >](https://reader036.fdocuments.net/reader036/viewer/2022081504/56649c815503460f94939a41/html5/thumbnails/3.jpg)
3
Outline Materi
• Rancangan Basis Relasi
• Rancangan Representasi Data
• Rancangan Kendala Perusahaan
• Analisis Transksi
• Pemilihan Organisasi File
• Pemilihan Indeks
• Estimasi Kebutuhan Disk Space
![Page 4: 1 Pertemuan > > Matakuliah: >/ > Tahun: > Versi: >](https://reader036.fdocuments.net/reader036/viewer/2022081504/56649c815503460f94939a41/html5/thumbnails/4.jpg)
4
Rancangan Fisikal
Proses produksi untuk menguraikan implementasi database pada secondary storage; basis relasi, organisasi file, penggunaan indek untuk mengefisienkan access data, penentuan kendala perusahaan dan sistem keamanan.
![Page 5: 1 Pertemuan > > Matakuliah: >/ > Tahun: > Versi: >](https://reader036.fdocuments.net/reader036/viewer/2022081504/56649c815503460f94939a41/html5/thumbnails/5.jpg)
5
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
data – Step 4.3 Design enterprise constraints
![Page 6: 1 Pertemuan > > Matakuliah: >/ > Tahun: > Versi: >](https://reader036.fdocuments.net/reader036/viewer/2022081504/56649c815503460f94939a41/html5/thumbnails/6.jpg)
6
Overview of Physical Database Design
Methodology
• Step 5 Design physical representation– Step 5.1 Analyze transactions– Step 5.2 Choose file organizations– Step 5.3 Choose indexes– Step 5.4 Estimate disk space
requirements
![Page 7: 1 Pertemuan > > Matakuliah: >/ > Tahun: > Versi: >](https://reader036.fdocuments.net/reader036/viewer/2022081504/56649c815503460f94939a41/html5/thumbnails/7.jpg)
7
Overview of Physical Database Design
Methodology
• Step 6 Design user views
• Step 7 Design security mechanisms
• Step 8 Consider the introduction of controlled redundancy
• Step 9 Monitor and tune the operational system
![Page 8: 1 Pertemuan > > Matakuliah: >/ > Tahun: > Versi: >](https://reader036.fdocuments.net/reader036/viewer/2022081504/56649c815503460f94939a41/html5/thumbnails/8.jpg)
8
Step 4 Translate Global Logical Data Model for
Target DBMS
To 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 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.
![Page 9: 1 Pertemuan > > Matakuliah: >/ > Tahun: > Versi: >](https://reader036.fdocuments.net/reader036/viewer/2022081504/56649c815503460f94939a41/html5/thumbnails/9.jpg)
9
DBDL for the PropertyForRent Relation
![Page 10: 1 Pertemuan > > Matakuliah: >/ > Tahun: > Versi: >](https://reader036.fdocuments.net/reader036/viewer/2022081504/56649c815503460f94939a41/html5/thumbnails/10.jpg)
10
PropertyforRent Relation and Staff Relation with Derived Attribute noOfProperties
![Page 11: 1 Pertemuan > > Matakuliah: >/ > Tahun: > Versi: >](https://reader036.fdocuments.net/reader036/viewer/2022081504/56649c815503460f94939a41/html5/thumbnails/11.jpg)
11
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. Example:
CONSTRAINT StaffNotHandlingTooMuchCHECK (NOT EXISTS (SELECT staffNo
FROM PropertyForRentGROUP BY staffNoHAVING COUNT(*) > 100))
![Page 12: 1 Pertemuan > > Matakuliah: >/ > Tahun: > Versi: >](https://reader036.fdocuments.net/reader036/viewer/2022081504/56649c815503460f94939a41/html5/thumbnails/12.jpg)
12
Step 5 Design Physical Representation
To determine optimal file organizations to store the base relations and the indexes that are required to achieve acceptable performance; that is, the way in which relations and tuples will be held on secondary storage.
![Page 13: 1 Pertemuan > > Matakuliah: >/ > Tahun: > Versi: >](https://reader036.fdocuments.net/reader036/viewer/2022081504/56649c815503460f94939a41/html5/thumbnails/13.jpg)
13
Analisis Transaksi Pada Relasi
![Page 14: 1 Pertemuan > > Matakuliah: >/ > Tahun: > Versi: >](https://reader036.fdocuments.net/reader036/viewer/2022081504/56649c815503460f94939a41/html5/thumbnails/14.jpg)
14
Transaction Usage Map for Some Sample Transactions Showing
Expected Occurrences
![Page 15: 1 Pertemuan > > Matakuliah: >/ > Tahun: > Versi: >](https://reader036.fdocuments.net/reader036/viewer/2022081504/56649c815503460f94939a41/html5/thumbnails/15.jpg)
15
Example Transaction Analysis Form
![Page 16: 1 Pertemuan > > Matakuliah: >/ > Tahun: > Versi: >](https://reader036.fdocuments.net/reader036/viewer/2022081504/56649c815503460f94939a41/html5/thumbnails/16.jpg)
16
Step 5.2 Choose File Organizations
To determine an efficient file organization for each base relation.
• File organizations include Heap, Hash, Indexed Sequential Access Method (ISAM), B+-Tree, and Clusters.
![Page 17: 1 Pertemuan > > Matakuliah: >/ > Tahun: > Versi: >](https://reader036.fdocuments.net/reader036/viewer/2022081504/56649c815503460f94939a41/html5/thumbnails/17.jpg)
17
Step 5.3 Choose Indexes
To determine whether adding indexes will improve the performance of the system.
• One approach is to keep tuples unordered and create as many secondary indexes as necessary.
![Page 18: 1 Pertemuan > > Matakuliah: >/ > Tahun: > Versi: >](https://reader036.fdocuments.net/reader036/viewer/2022081504/56649c815503460f94939a41/html5/thumbnails/18.jpg)
18
Step 5.3 Choose Indexes
• Another approach is to order tuples in the relation by specifying a primary or clustering index.
• In this case, choose the attribute for ordering or clustering the tuples as:– attribute that is used most often for join
operations - this makes join operation more efficient, or
– attribute that is used most often to access the tuples in a relation in order of that attribute.
![Page 19: 1 Pertemuan > > Matakuliah: >/ > Tahun: > Versi: >](https://reader036.fdocuments.net/reader036/viewer/2022081504/56649c815503460f94939a41/html5/thumbnails/19.jpg)
19
Step 5.3 Choose Indexes
• If ordering attribute chosen is key of relation, index will be a primary index; otherwise, index will be a clustering index.
• Each relation can only have either a primary index or a clustering index.
• Secondary indexes provide a mechanism for specifying an additional key for a base relation that can be used to retrieve data more efficiently.
![Page 20: 1 Pertemuan > > Matakuliah: >/ > Tahun: > Versi: >](https://reader036.fdocuments.net/reader036/viewer/2022081504/56649c815503460f94939a41/html5/thumbnails/20.jpg)
20
Step 5.4 Estimate Disk Space Requirements
To estimate the amount of disk space that will be required by the database.
![Page 21: 1 Pertemuan > > Matakuliah: >/ > Tahun: > Versi: >](https://reader036.fdocuments.net/reader036/viewer/2022081504/56649c815503460f94939a41/html5/thumbnails/21.jpg)
21
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 lifecycle.
![Page 22: 1 Pertemuan > > Matakuliah: >/ > Tahun: > Versi: >](https://reader036.fdocuments.net/reader036/viewer/2022081504/56649c815503460f94939a41/html5/thumbnails/22.jpg)
22
Step 7 Design Security Measures
To design the security measures for the database as specified by the users.