Your supervisor has approved your normalized versions of the database. Your team members were given copies. One of the members has sent you an e-mail with the given problems:
describe why are there so many more foreign keys in the third normal form than in the first? Is this always going to be true? Why is it significant to define the primary keys of a file correctly? What happens to the third normal form when they are wrongly defined? Some designers will state that to make an address file into third normal form, you must take out the city and state, place it to a different table, and link it by zip code. What merits and demerits are there to this? When normalizing a table which can have a many-to-many relationship with the other table, what steps should you take? What are the merits of third normal form for applications with a lot of changes to the database, like a data entry program? What are the demerits of third normal form for an application which does a lot of reporting on a stable database like general ledger month-end reporting?