Is Entity Framework good for bigger Database? -

i used entity framework database having around 50 tables , worked fine.

but see happens larger database in terms of number of tables/entities tried implement entity framework database had around 100+ tables. once selected tables , clicked on finish button on entity framework wizard hanged vs 2010 not results.

my questions below;

1.if have larger database in terms of table/entites described above, idea use entity framework?

2.what better approch using entity framework work database?

3.should create multiple datacontext or edmx files lesser entites in it?

4.how these different datacontext interact each other?

5.is there recommended no of tables should used while working entity framework?

@will correct limitation you're seeing in designer, it's not one, code-first doesn't fix problem.

if designer seems slow, it's inconvenient, not end of world. runtime performance considerations thing altogether. performance-critical tasks , tuning, you'll want understand whole pipeline.

view generation, e.g., takes time. can move compile time manual work.

1.if have larger database in terms of table/entites described above, idea use entity framework?

i wouldn't let stop you.

2.what better approch using entity framework work database? 3.should create multiple datacontext or edmx files lesser entites in it?

that's approach many applications.

4.how these different datacontext interact each other?

mostly not. a single, giant data model bad idea due service coupling. however, can selectively couple them sharing portions of models includes in edmx or classes in code-first.

5.is there recommended no of tables should used while working entity framework?

one way use smaller models, you've suggested. way work around runtime performance issues sometimes come larger models (see links give above). potential performance "problem", write correct code first, profile , fix slow parts. usually, query tuning more important model size anyway.