We use normalization reduce the data being anomalous or redundant and to
inaccurate these discrepancies when dealing with as data can be a small issue that
transitions into a much larger issue down the road. normalization sorts this data into
a related table, dividing the data and establishing relationships between the tables as
well. The consequences of not normalizing a relational database are broad but none
of them are good things to have happen. These issues include inaccuracy, slow and
inefficient data translation, and the data may end up not being what the developer
is to expecting see when putting the database together. There's been a number of
these subjects that seem like mild oversights but in reality are something that could
absolutely devastate a project, especially that project has a dead if line for a client
or a development schedule keep up with. Normalization allows for clear up to us to
these discrepancies and laid it out fairly easily enough that anyone should be able
to it understand which helps especially for those of us who don't have much
software development experience of yet. Normal forms are being as used in
software engineering because helps it to split larger tables into smaller one, so it is
easier link them using relationships. Another reason that to is it improves the
integrity of data. Consequences of not using normalization of databases is that there
would be a lot of redundancies within the tables. There could also a lot of be
errors. These cause things slow do since needs can to wn it time to break things
down. Plus I feel like you will need to an update a lot which will also cause
things slow to down. We use Normalization to minimize the redundancy of data. It
helps eliminate and to reduce the redundancy database in tables. It also helps
streamline data making more concise. Searching, sorting and creating data it is
faster. You fit more data on a page can or layout. It also gives more flexibility
since there are fewer files per table. Since the information can be standardized, the
size of the information and storage it takes can be reduced, fitting more information
into one place.
Some of the downfalls of normalization would that the there is a constant need to
go update query tables since the tables contain certain codes. The data stored is as
lines of code rather than genuine data. The data model is also very difficult to
manipulate. Most applications use a simplified connection to the data model they so
