For a number of reasons, normalizations is not often an advantage for – McqOptions

MCQOPTIONS

1.	For a number of reasons, normalizations is not often an advantage for a(n) ________ database.
A.	read-only
B.	updateable
C.	either a read-only or an updateable
D.	None of the above is correct.
Answer» B. updateable

Discussion

No Comment Found

Related MCQs

We can eliminate modification anomalies with proper normalization that results in tables in BCNF.
Denormalized tables are in BCNF.
Normalization requires programmers to write more complex SQL.
In all cases, normalization into BCNF is desirable.
We use the SQL construct COUNT(*) to count the number of rows in a table.
When building a database from an existing set of tables, we may safely assume that there are no multivalued dependencies in the data we are given.
One common design problem when designing a database from existing data is the presence of missing values, called blank values, in received data.
Proper normalization eliminates duplicated data.
When you are given a set of tables and asked to create a database to store their data, the first step is to create the new database.
The phrase "SALE.CNumber must exist in CUSTOMER.CNumber" is a referential integrity constraint.