This week we learned lots about the decomposition of our relations we are creating in the database as well how to make the relations into normal forms, which there are three normal forms. I learned that there can be data that is redundant and therefore not useful for the database. This data has no integrity and can be misplaced and even confuse how the data can be used and retrieved. This type of problem must be avoided.
I had a hard time understanding how the breaking down of one relation into two or more would help keep all the data from being redundant. Learning new ways in which to update and even delete new or old data can be a problem if we do not have our relations in order so that we are not collecting useless data shoved into one relation. Therefore, making it hard to separate. I struggled when it came time to decompose our existing relations further than they already were. The librarian relation to me was fine just the way it was, but I know there is some other way to separate non like data to keep it together through many to one relations. Although the librarian relation is unary I still can’t grasp how to decompose it.
One of …show more content…
There must be wire frames and even putting pencil to paper to get the overall look at what the end result of the database will be and how it will be used. Honestly, the thought and planning that goes into the architecture of a database if far more complex than I thought it would be. However, the takeaway from this week is that doing the simple things like breaking and address into city state zip code and making the relation that only has the necessary information needed for a tuple then taking other outside information and making it into its on relation will save lots of headaches in the future or any database no matter how small or
I had a hard time understanding how the breaking down of one relation into two or more would help keep all the data from being redundant. Learning new ways in which to update and even delete new or old data can be a problem if we do not have our relations in order so that we are not collecting useless data shoved into one relation. Therefore, making it hard to separate. I struggled when it came time to decompose our existing relations further than they already were. The librarian relation to me was fine just the way it was, but I know there is some other way to separate non like data to keep it together through many to one relations. Although the librarian relation is unary I still can’t grasp how to decompose it.
One of …show more content…
There must be wire frames and even putting pencil to paper to get the overall look at what the end result of the database will be and how it will be used. Honestly, the thought and planning that goes into the architecture of a database if far more complex than I thought it would be. However, the takeaway from this week is that doing the simple things like breaking and address into city state zip code and making the relation that only has the necessary information needed for a tuple then taking other outside information and making it into its on relation will save lots of headaches in the future or any database no matter how small or