Which guideline helps in determining fields for a table?

Which guideline helps in determining fields for a table?

• A. Relate each field directly to the subject of the table
• B. Don't include derived or calculated data
• C. Store information in the smallest logical parts
• D. Use calculated fields

Answer: (A)

The main idea is to design a table around a single subject, and each field should be an attribute of that subject. By relating every field directly to what the table is about, you keep the data focused, consistent, and easy to query. This aligns the table with a clear real-world concept, which helps with data integrity and straightforward normalization. Other considerations, like avoiding derived data in base fields or breaking data into the smallest atomic pieces, are important design practices too, but they don’t determine which fields belong as directly as ensuring each field describes the table’s subject. Calculated fields can be used, but they’re often best produced when needed rather than stored as raw fields.

The main idea is to design a table around a single subject, and each field should be an attribute of that subject. By relating every field directly to what the table is about, you keep the data focused, consistent, and easy to query. This aligns the table with a clear real-world concept, which helps with data integrity and straightforward normalization.

Other considerations, like avoiding derived data in base fields or breaking data into the smallest atomic pieces, are important design practices too, but they don’t determine which fields belong as directly as ensuring each field describes the table’s subject. Calculated fields can be used, but they’re often best produced when needed rather than stored as raw fields.