Cs 331 Exercise 4a
Cs 331 Exercise 4a
=====================================================================================
D) Data layout
12) An integrity control supported by a DBMS is:
A) substitute estimates.
B) security.
C) range control.
D) GUI guards.
13) The value a field will assume unless the user enters an explicit value for an instance
of that field is called a(n):
A) default value.
B) null value.
C) range control.
D) gurand.
14) A method for handling missing data is to:
A) substitute and estimate for the missing data.
B) track missing data with special reports.
C) perform sensitivity testing.
D) all of the above.
15) Sensitivity testing involves:
A) checking to see if your teeth hurt when you brush.
B) seeing how accurate data are.
C) checking to see if missing data will greatly impact results.
D) none of the above.
16) All of the following are common denormalization opportunities EXCEPT:
A) two entities with a one-to-one relationship.
B) a one-to-many relationship.
C) a many-to-many relationship with nonkey attributes.
D) reference data.
17) In most cases, the goal of ________ dominates the design process.
A) efficient data processing
B) security
C) quick pointer updates
4
D) Final
24) A form of denormalization where the same data are stored in multiple places in the
database is called:
A) data duplication.
B) data replication.
C) advanced placement.
D) horizontal partitioning.
25) Within Oracle, the named set of storage elements in which physical files for database
tables may be stored is called a(n):
A) extent.
B) table.
C) tablespace.
D) partition.
26) While Oracle has responsibility for managing data inside a tablespace, the tablespace
as a whole is managed by the:
A) user.
B) database administrator.
C) application developer.
D) operating system.
27) A contiguous section of disk storage space is called a(n):
A) track.
B) sector.
C) extent.
D) tablespace.
Answer: C
28) A(n) ________ is a field of data used to locate a related field or record.
A) key
B) index
C) lock
D) pointer
29) A(n) ________ is a technique for physically arranging the records of a file on
6
=====================================================================
Part2
====================================================================
1 Discuss the critical decisions that must be made during physical database design.
Selecting the proper storage format for the data to be saved in the database is one of the crucial
decisions.
And choosing the data type for each attribute within the logical model.
And aggregating attributes from the logical data model to produce physical records.
Providing the freedom to add new performance-enhancing tactics. These are the crucial
decisions that must be taken during the physical database design process
2 Discuss why physical database design is a foundation for compliance with regulations
on financial reporting.
Financial reporting is a must-manage, plan, and record. So to create its total record and database,
it must be robust and have the required constraints to secure and remove redundancy from such
critical reports, so physical database design comes into play.
7
Physical database design optimizes performance, has required data integrity, and removes
redundancy. And managing financial data is a never-ending task, but physical databases can
handle it.
It's the basis for financial reporting.
Statistics on data volume and frequency of use are critical inputs into the physical database
design process, especially for very large-scale database implementations.
Data volume and usage analysis is not a one-time static activity; rather, significant changes in
usage and data volumes must be monitored on a continuous basis. As a result, database
professionals must have a thorough understanding of the database's size and usage patterns
throughout its life cycle.
Adding notation to the EER diagram, which represents the final set of normalized relations from
logical database design, is an easy way to show statistics about data volumes and usage.
A Data Type is a specific coding scheme that is understood by system software, such as a
DBMS, to be used in the representation of data pertaining to an organization.
The end user is typically not concerned with the bit pattern of the coding scheme; however, the
physical database design must take into consideration the amount of space necessary to store data
as well as the speed required to access data.
Different database management systems provide a selection of distinct data types for use in a
relation's or table's fields and attributes.
When choosing a data type, there are four goals to keep in mind:
Represent all of the possible values, improve data integrity, enable all of the possible data
manipulations, and reduce the amount of space needed for storage.
8
A field with a small number of possible values or extremely large values can be converted into a
code that requires less space. This will reduce the available space on the field.
The Coded Table is absent from the conceptual and logical models. It is a physical structure
designed to enhance data processing performance and not a collection of data with business
value.
Numerous DBMSs rely on the physical structure of the fields to ensure data integrity (i.e.,
controls on the possible value a field can assume).
The data type imposes one form of data integrity control by limiting the type of data (numeric or
character) and the size (or length) of a field value.
Default Value
It is the value a field assumes when a user does not enter a value for a particular instance of that
field.
Assigning a default value to a field can reduce data entry time by allowing the user to skip
entering a value.
Additionally, it can reduce data entry errors for the most frequent value.
Range control
A range control restricts the allowed values for a field. The range may be a range of numbers or a
list of specific values.
Null value control
A null value is defined as an empty or unavailable value.
The value of the primary key attribute cannot be null.
Referential consistency
Referential integrity is a form of range control in which the value of a field must exist in another
row of the same or (more commonly) a different table.
9
Tablespaces are the logical entity in our database and store logically organized data in datafiles.
They are referred to as logical storage units because they are hidden from the operating system's
file system. Only one database is associated with a tablespace, and at least one datafile is used to
store tablespace data. Tablespaces can also be defined as logical storage units comprised of one
or more datafiles. There can be up to 1022 datafiles per tablespace. This number depends on your
operating system.