I've got a project that interacts having a database through ADO.internet Data Services. The database is big (almost 150 tables with dependencies). The project began a couple of years back and there have been DataSets used then now we are moving towards entity model associations. The model keeps growing since we're adding more tables we have to use. Is the right method to manage everything?. Meaning should I've got a SINGLE database model file to possess single data context?

What exactly are disadvantages and just how do you apply the entity framework with large databases (or should it 't be combined with large ones?

The disadvantages I see are:

  • Visual Studio 2010 begins to freeze when opening that large XML within the designer (maybe this isn't an issue, because despite many tables it does not freeze for very long time).
  • It might be difficult to find references in the model (though F4 + qualities window's combobox of object names almost removes this search related problem).

PS, strange that nobody solutions. The question appears important as well as in simple words I'll just rephrase it: What's best, one type of whole an entire, large database or several types of that database?

I suspect you are not getting many solutions since it is not really a large problem. Even just in your disadvantages you say they are not necessarily problems. Certainly EDM is okay dealing with large databases. I'd argue the bigger the database the greater the requirement for an ORM solution.

However you could have one model split over multiple files in the event that is needed you retain things organised - i.e. multiple .edmx files can constitute just one data context.

Alternatively if you're able to realistically split the model into isolated parts that may interact via connects instead of requiring to directly join organizations within the data context that's great for both controlling the entity data model, as well as only for fundamental separation of concerns.