Go on. Explore!

lvl 0 • 0 xp

lvl 1

Home Market Decks Interests

Chapter 08 Quiz

memorize.ai (lvl 286)

(0)

10 cards

()

Section 1

Preview this deck

a c

Front

1 / 10

SQL

0.0

0 reviews

5			0
4			0
3			0
2			0
1			0

Active users

All-time users

Favorites

Last updated

6 years ago

Date created

Mar 1, 2020

Cards (10)

Section 1

(10 cards)

a c

Front

physical database design a. immediately follows the logical design stage b. immediately follows the requirements-gathering stage c. is done in parallel with the definition of the hardware and system software required for the application system d. can be done without a corresponding logical design e. includes the design of application programs

Back

d e

Front

relationships in the logical model a. are enforced with triggers in the physical design b. require NOT NULL constraint in the physical model c. become check constraints in the physical model d. become a primary key in the parent table and a foreign key in the child table e. become referential constraints in the physical model

Back

c d e

Front

precision and scale a. apply to all data types b. can be used to prevent negative numbers in numeric columns c. can be used to prevent decimal digits in columns that should contain only integers d. can be used to prevent numbers that are too small from being stored in a column e. can be used to prevent numbers that are too large from being stored in a column

Back

b c e

Front

indexes a. are slower to sequentially scan than corresponding tables b. are usually smaller than the tables they reference c. may be used to assist with primary key constraints d. may be used to improve insert, update, and delete performance e. may be used to improve query performance

Back

a b c e

Front

view restrictions include a. if a view omits a mandatory column that has no default, inserts to the view are not possible b. any update involving a view may only reference columns from one table c. privileges are required in order to update data using views d. views containing joins can never be updated e. updates to calculated columns in views are prohibited

Back

a c

Front

referential constraints a. should have descriptive names b. are always defined on the parent table c. define relationships identified in the logical model d. name the parent and child tables and the foreign key column e. require that foreign keys be defined as NOT NULL

Back

b c d

Front

when you're designing tables a. unique identifiers become triggers b. each attribute in the relation becomes a table column c. each normalized relation becomes a table d. primary key columns must be defined as NOT NULL e. relationships become check constraints

Back

b d e

Front

supertypes and subtypes a. only apply to the logical design b. usually have the same primary key in the physical tables c. must be implemented exactly as specified in the logical design d. may have the supertype columns folded into each subtype in the physical design e. may be collapsed in the physical database design

Back

b c

Front

unique constraints a. may only be defined once per table b. force column values to be unique within the table c. are usually implemented using an index d. are identical to primary key constraints e. require columns that have NOT NULL constraints

Back

a b c

Front

check constraints a. may be used to force a column to match another column in the same row b. may be used to force a column to match a list of values c. may be used to force a column to match a range of values d. may be used to enforce a foreign key constraint e. may be used to force a column to match a column in another table

Back