1. Class,
The disadvantage of normalizing a database to a high degree of
normalization would include structural disadvantages such as
breaking the database down into too many granular tables.
When this occurs you may end up having to create more
complex queries to the join the data that has been scattered
across multiple tables. Another disadvantage would be reduced
efficiency which is due to the data residing on multiple tables
which will cause the system to work harder when a report is
requested because of all data it needs to extract from the
multiple locations. The parts for the system that it requires to
work harder are the CPU's and hard drives ultimately slowing
the system down reducing its efficiency.
Getting rid of redundant data and inconsistent dependencies can
reduce the size of your database system. However, doing this
very act may incur a new cost for the organization when you
restructure your tables within the database itself. The
stakeholders must work with the Data Analyst to understand
normalization and perform detailed analysis before even
beginning to normalize the data if the system is a complex
system. It is also possible to over-normalize a database and
break it down into too many tables which will create its own set
of problems. What could be some examples of this?