Flexible structure for decision support systems

High efficiency in large transaction processing

Powerful data manipulation capabilities

Easy to understand and use

A foreign key in the "many" side only

An intersection table with two foreign keys

An associative attribute in the "one" side

A unique foreign key in both related tables

many-to-many relationship

one-to-many relationship

All options are correct

one-to-one relationship

Every relation must have a primary key.

Composite primary keys can consist of multiple columns.

Primary keys can contain null values.

Primary keys must be unique for every row in the table.

When updating information requires changes in multiple rows.

When deleting a row causes unintended data loss.

When redundant data is present across multiple rows.

When a new record cannot be added due to a missing value in a required field.

A key automatically generated by the DBMS to uniquely identify a row.

A non-key attribute that appears as a primary key in another relation.

A key that serves as both primary and foreign key in the same table.

A key that is derived from combining multiple attributes.