Tell me more ×  A common approach to data modelling is to use a
data modelling tool (e.g. Erwin) to generate a schema, and then
from the schema to generate business objects using an object
relational mapper (ORM).  Less common is the reverse process
where the data modelling is done using business objects (e.g.
POCO/POJO's), from which the schema is generated using an ORM.
This question is asked in relation to non-trivial systems that
comprise hundred's of database tables.  I'm under the impression
that many designers/architects stay away from the second
approach because of a number of hidden issues, for example data
migration between schema revisions, reduced control over
designing and tuning SQL queries. What are the real issues?
share|improve this question In my limited experience with the
latter, I consistently find a lack of foreign key relationships
defined utterly disturbing. –  OMG Ponies Sep 22 '09 at 6:15 add
comment  1 Answer  up vote 1 down vote accepted  For me usually
the real issue is this sta