Not sure it's an either/or question -- there's nothing wrong with starting with a DB design in an ERM, creating a working first take DB based on it, then re-factoring the DB and the ERM whenever you make changes, whether for normalization or any other reasons. To paraphrase Kool and the Gang, "Iterate. Iterate. Dance to the music."