C
corentin Vimont
Hello all,
We are trying to migrate to Linq to Entity for managing access to an SQL
Database. We are experiencing problems when dealing with an EDMX model
containing a lot of entities and relations between entities. Everything
works fine when we add 50 entities to the model, with an average of 2
Foreign keys per entity, but when adding 700 entities, the EDMX seems to
be overwhelmed and refuses to continue.
We have already tried the method consisting of splitting the model into
several thematic models, but are not satisfied with this, as we are
working on an ERP project, almost every table will have to be accessible.
We have already tried removing all the relations between the entities in
the model in order to lighten the requested memory, but Linq looses
most of it interest without FK management…
This point could force us to adopt another technology for accessing
databases if we don’t find other ideas. Does someone know a better way
of managing large model with several hundreds of entities without being
limited as we are now? We are surely not the first developer team using
Linq to Entity on a large database?
Thanks in advance for your answers.
Corentin Vimont
We are trying to migrate to Linq to Entity for managing access to an SQL
Database. We are experiencing problems when dealing with an EDMX model
containing a lot of entities and relations between entities. Everything
works fine when we add 50 entities to the model, with an average of 2
Foreign keys per entity, but when adding 700 entities, the EDMX seems to
be overwhelmed and refuses to continue.
We have already tried the method consisting of splitting the model into
several thematic models, but are not satisfied with this, as we are
working on an ERP project, almost every table will have to be accessible.
We have already tried removing all the relations between the entities in
the model in order to lighten the requested memory, but Linq looses
most of it interest without FK management…
This point could force us to adopt another technology for accessing
databases if we don’t find other ideas. Does someone know a better way
of managing large model with several hundreds of entities without being
limited as we are now? We are surely not the first developer team using
Linq to Entity on a large database?
Thanks in advance for your answers.
Corentin Vimont