Is normalization necessary or not?

Normalization is one of process in database design. It separate complexs table in ER-Diagram into several table by consider field dependence and break down table for make each field is independent.

It step are 1NF --> 2 NF -->3NF -->BCNF-->4NF-->5NF. The end point or last step of normalization are depend on type of database or on business, largely, the last step is BCNF. Many to Many relationships between table are not appropriate because It would make maintenance and expand database difficultly ,and data anomaly will occurred. It is make every table in relationship is One to many or Many to Many, so It will help to prevent data anomaly. It usually perfrom for optimize transaction table in database.

Normalization is very good to optimize table, but It is not appropriate in any type of database such simple data collection ,etc. If we design database table well, we won't to normalize table. I think ,we usually normalize database when we need to change database structure in our business. It may not improve database and application efficiency, so to improve database and application efficiency, Denormalization is one way to do it.Although we able to normalize but DATA ANOMALY is not vanished.

IN MY MINI-PROJECT ... NORMALIZATION IS NOT NECESSARY.
I am sure in my database design, because my mini-project will collect simple girl(MOE) information . girls in my database are don't have to bill or other transaction information. My database is collect only entity type of database. I had normalize my database at once,but result is very bad, because fine-grained normalized database is very complexily.