Working With Large Models In Entity Framework – Part 2

Comment contourner le problème de performance des très gros modèles (2)

Matthieu MEZIL — Wed, 26 Nov 2008 18:37:24 GMT

Srikanth Mandadi a publié la deuxième partie de sa série relative au problème de performances des très

re: Working With Large Models In Entity Framework – Part 2

Travis Plummer — Wed, 26 Nov 2008 21:13:24 GMT

We appreciate your efforts addressing this issue. I think that alot of folks would like to see a much more simplified approach in the long term. My hope is that the Oslo repository has a key role to play here. Especially in terms of dividing the models up into sub domains, being able to reuse them among teams and the like. In fact would it be possible for your team to let us know how they see the relationship between EF , M, and the Oslo repository? Just know that we're looking for something more than modifying the EDMX files by hand.

Thanks,

Travis

re: Working With Large Models In Entity Framework – Part 2

Andrea Bianchi — Thu, 27 Nov 2008 17:53:41 GMT

It's a start.

But i'm interessing in possibility to have multiple programmers work whith a multiple file (like multiple .edmx) that combine in unique edmx in compile time.

Each programmers can use a personal file to describe CSDL SSDL & MSL of this part of the application (like for a single class).

In your scenario A) SSDL and MSL are unique and not alow concurrency.

I want the possibility of paraller developper but I don't want to manage manually association like in scenario B.

it's possible to merge multiple edmx in one?

Have we thinking at tool to do this?

re: Working With Large Models In Entity Framework – Part 2

Malcolm Sheridan — Fri, 28 Nov 2008 05:42:20 GMT

It is a step in the right direction, but there are quite a few steps involved, and this would increase the tendency to make a mistake.

Can you make the process easier in v2?

re: Working With Large Models In Entity Framework – Part 2

Srikanth Mandadi — Tue, 02 Dec 2008 11:09:00 GMT

Malcolm,

We have talked about quite a few things that would improve this process. But other than a few small things here and there, some of the big items that we want to do in this area like designer support for Using etc probably won't make it into V2.

Thanks

Srikanth

re: Working With Large Models In Entity Framework – Part 2

Srikanth Mandadi — Tue, 02 Dec 2008 11:18:18 GMT

Andrea,

I did not completely follow the scenario you are describing but my guess is that you are talking about allowing users to split and/or reuse their SSDL and MSL files as we allow them to do in the CSDL. If so, this is something we talked about and something we want to enable in the future.

Thanks

Srikanth

Weekly digest of interesting stuff

Steve Strong's Blog — Wed, 03 Dec 2008 23:44:18 GMT

Weekly digest of interesting stuff

re: Working With Large Models In Entity Framework – Part 2

RezRaider — Mon, 08 Dec 2008 22:30:25 GMT

Srikanth,

In your option "b", step 5 (where you create a new CSDL called CustomerBase), I am not understanding this.

First, I need to incorporate your second option (b) into my application. I'm splitting into 3 separate models as I have over 250 tables in my app, but I need to share a table called Account across two of the models. All 3 of these models will be referenced in the one application.

Here's my confusion: When you create separate models, these models are EDMX files, not CSDL, SSDL and MSL files. I do understand that the EDMX is comprised of these 3 components. But your instructions say (in step 5) to add a CSDL file called CustomerBase. How do you do that? Are you really saying to add another MODEL called CustomerBase, modify the CSDL section of the CustomerBase.edmx, then add "using" in the other 2 models (CustmerDetails, ProductDetails)?

Please let me know as I am trying to do this in my application in order to solve the performance issues with my overly large model.

Thanks,

Rez

re: Working With Large Models In Entity Framework – Part 2

Andrea Bianchi — Tue, 09 Dec 2008 13:01:30 GMT

Hi Srikanth,

you perfectly understood what i mean to say.

I'm happy that this feature will be (soon? ;) ) available!

It's great that lead developer read our requests (or feedback) and answer to our needs!

Thank's again.

Good work.

Andrea.

解决Entity Framework中大数据模型问题的技巧

BrianLei — Wed, 10 Dec 2008 16:36:33 GMT

EntityFramework的开发领导SrikanthMandadi称这个包含两部分内容的文章为

Entity Framework - очумелые ручки или как добавть новую таблицу

Заметки о Net технологиях — Wed, 21 Jan 2009 14:35:29 GMT

Привет всем! В заметке Working With Large Models In Entity Framework – Part 2рассказано о декомпозиции...

re: Working With Large Models In Entity Framework – Part 2

MikeBB — Thu, 22 Jan 2009 12:11:50 GMT

Hi! *.msl may be split easy, but how split *.ssdl?

Problem with Large Models in Entity Framework (and LINQ to SQL)

Eric's Blog — Wed, 18 Feb 2009 09:50:48 GMT

After a year of working with LINQ to SQL, I strongly belivev that LINQ to SQL and Entity Framework (EF)

Entity Framework ottimizzare le performance

Pietro Brambati Blog — Wed, 08 Apr 2009 17:43:40 GMT

Direi che una buona pagina da cui partire è questo documento su MSDN :Performance Considerations for

Comment découper ses entités en plusieurs modèles

Matthieu MEZIL — Wed, 27 May 2009 02:47:53 GMT

Un de mes clients veut développer un ERP avec EF. Sa base contient plus de 600 tables quasiment toutes

How to split your EDM?

Matthieu MEZIL — Wed, 27 May 2009 16:28:15 GMT

One of my customers wants to code an ERP. To make it, he wants to use EF. His DB has more than 600 tables

Как разделить EDM на несколько частей?

Stump's workshop — Fri, 05 Jun 2009 08:16:53 GMT

Похоже, народ начинает пробовать заюзать Entity Framework в реальных проектах. И начинает задавать неудобные...

re: Working With Large Models In Entity Framework – Part 2

Dhileep — Mon, 10 Aug 2009 16:16:48 GMT

Hi Srikanth,

We split our model into two and were working on this till recently. I tried refactoring the code and it is broken now. When i try to load the data from other mode i am getting an error like

"System.InvalidOperationException: The relationship 'DataAccess.EF.ParameterListValuesParameters' does not match any relationship defined in the conceptual model".

Do you have idea about this error? I searched in net for this error but no help.

re: Working With Large Models In Entity Framework – Part 2

Dhileep — Mon, 10 Aug 2009 16:19:30 GMT

By the way, I used your option B to create 2 sets of csdl, msl and ssdl files for the models and used "using" in the second model to refer the entities in the first model.

Thanks,

Dhileep

re: Working With Large Models In Entity Framework – Part 2

Koistya `Navin — Tue, 20 Oct 2009 21:03:00 GMT

Having one .edmx file might be good as far as it could be easily edited both manually and via designer.

- For the manual editing improvements you could add one simple feature which will provide some sort of "navigation links". Thus when you edit some peace of xml code related to some table in SSDL part, VS will show you links (or previews) of other related peaces of xml in CSDL and MSL part.

- In entity designer we need an ability to group entities into aggrigates with different namespaces. (ex.: Membership.User, Membership.Role, Store.Product, Store.CreditCard etc.). That would be great if we could collaps/expand those "aggrigates". Zoom in/out int0 aggrigates view and into entities view.

navin@php.net

re: Working With Large Models In Entity Framework – Part 2

Tooraj — Wed, 21 Oct 2009 12:59:25 GMT

Hi Srikanth,

Is there any fix for the "large model" issue in version 4?

re: Working With Large Models In Entity Framework – Part 2

Adam — Tue, 27 Oct 2009 18:04:01 GMT

Will any of the "large model" issues mentioned in Part I and Part II be addressed in the upcoming EF4 release? There is a lot of good information about some of the new features, but can you let us know if there is any movement towards making EF more friendly to large models? Or at least if there will be a less manual approach to splitting models in EF4?

My team is in the process of migrating an application with LOTS of tables. So far we only have ~80 tables in EF (out of 1,000+), but we will add more tables to the model as we add functionality. Unfortunately we couldn't add all of the tables to EF due to performance problems and others issues mentioned in these blog posts.

Thanks in advance for any information you can provide!