Physical Database Design Quiz

A requirement to begin designing physical files and databases is:

• normalized relations.

• physical tables created.

• implementation complete.

• all datatypes determined.

A key decision in the physical design process is:

• ignoring the size of the database.

• selecting structures.

• deciding on the monitor.

• deciding the e-r diagrams

Designing physical files requires ________ of where and when data are used in various ways.

• maps

• descriptions

• keys

• hints

A detailed coding scheme recognized by system software for representing organizational data is called a(n):

• DBMS code.

• data type.

• SQL.

• DB layout.

All of the following are objectives when selecting a data type EXCEPT:

• represent all possible values.

• improve data integrity.

• support all data manipulations.

• use a lot of storage space.

The smallest unit of application data recognized by system software is a:

• field.

• row.

• data type.

• column

An appropriate datatype for one wanting a fixed-length type for last name would include:

• VarChar.

• Char.

• Blob.

• Date.

An appropriate datatype for adding a sound clip would be:

• VarChar.

• Char.

• Blob.

• Date

The value a field will assume unless the user enters an explicit value for an instance of that field is called a:

• default value.

• null value.

• range control.

• gurand.