c# - Multiple/Single *.edmx files per database -

i have project interacts database through ado.net data services. database large (almost 150 tables dependencies). project started few years ago , there datasets used then; we're moving towards entity model relationships. model growing since adding more tables need work with. right way manage that?. meaning should have single database model file have single data context?

what drawbacks , how use entity framework large databases (or should not used large ones?

the disadvantages see are:

• visual studio 2010 starts freeze when opening large xml in designer (maybe not problem, because many tables doesn't freeze long time).
• it becomes hard find references in model (though f4 + properties window's combobox of object names removes search related problem).

ps, strange no 1 answers. question seems important , in simple words i'll rephrase it: better, 1 model of whole whole, large database or several models of database?

i suspect aren't getting many answers because it's not big problem. in both disadvantages they're not problems. edm fine working big databases. i'd argue larger database more need orm solution.

however can have 1 model split on multiple files if keep things organised - i.e. multiple .edmx files can constitute single data context.

alternatively if can logically split model isolated parts can interact via interfaces rather needing directly join entities in data context both managing entity data model, , basic separation of concerns.