We used a Database First approach in all our projects to model our domains (with EF4, in a banking company). We are starting a new project and we plan to embrace a Code First approach (with EF6). Is there any guideline, tool, or pattern you think we should follow to design the underlying database model accordingly to Data Patterns a DBA could advice (to prevent a "propery bag" database) ? What do you think are common pitfalls in this approach, for developers, DBAs, ALM... ?
Many thanks,
Aucun commentaire:
Enregistrer un commentaire