1. One relation per file, with fixed-length record, is good for small databases, which also reduces the code size.

2. Many large-scale DB systems do not rely directly on the underlying operating system for file management.One large OS file is allocated to DB system and all relations are stored in one file.

3. To effciently execute queries involving depositor 1 customer, one may store the depositor tuple for each cname near the customer tuple for the corresponding cname, as shown in Figure 10.19.

4. This structure mixes together tuples from two relations, but allows for ecient processing of the join.

5. If the customer has many accounts which cannot fit in one block, the remaining records appear on nearby blocks. This file structure, called clustering, allows us to read many of the required records using one block read.
6. Our use of clustering enhances the processing of a particular join but may result in slow processing of other types of queries, such as selection on customer.For example, the query

select *
from customer

now requires more block accesses as our customer relation is now interspersed with the deposit relation.

7. Thus it is a trade-o , depending on the types of query that the database designer believes to be most frequent.Careful use of clustering may produce significant performance gain.