Question

How do you recognize the difference between good and bad structures? What role does normalization play in good and bad table structures, and why is normalization so important to a good table structure?

Answer 1

`Hey,

Note: Brother if you have any queries related the answer please do comment. I would be very happy to resolve all your queries.

A good structure is internally used by a host transact or a program whereas the bad tables generate the source as a background. The only difference is a table is permanently in hold of datawhile a structure only holds the running data.

The bad structures work under a principle of duplicate, and this leads to the space wastage and anincrease in likelihood of errors together with inconsistencies. A good structure always provides full information on subjected- based tables in order to reduce the duplicated data. Also a good structure attributes to an accommodation of the processed data and the reporting needs.

Normalization ensures that attributes are grouped together in such a way that there is no redundancy or at least controlled redundancy. ... The bottom line is “each table should have only one source of data” if it is in the normal form. We aim at good database design. This means good table structures.

Kindly revert for any queries

Thanks.