<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Working With Large Models In Entity Framework – Part 2</title><link>http://blogs.msdn.com/b/adonet/archive/2008/11/25/working-with-large-models-in-entity-framework-part-2.aspx</link><description>In my last post I talked about some of the issues you typically face when using a large Entity model in your application. I have also described a few things that you can use to mitigate some of these problems. In this post I will walk through a couple</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Working With Large Models In Entity Framework – Part 2</title><link>http://blogs.msdn.com/b/adonet/archive/2008/11/25/working-with-large-models-in-entity-framework-part-2.aspx#10255775</link><pubDate>Thu, 12 Jan 2012 01:49:03 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10255775</guid><dc:creator>John Rusk</dc:creator><description>&lt;p&gt;With the &amp;quot;using&amp;quot; approach, how does that affect the startup performance of the app? &amp;nbsp;Currently, we have one big edmx, and start-up performance is bad, because EF 4.2 processes the whole model at startup. (even with pre-generated views it is still too slow). &amp;nbsp;With the using approach, will EF only process stuff from one diagram on startup (i.e. process the stuff from one diagram the first time something on that diagram is queried) or will it still process all the metadata for the whole application at startup?&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10255775" width="1" height="1"&gt;</description></item><item><title>re: Working With Large Models In Entity Framework – Part 2</title><link>http://blogs.msdn.com/b/adonet/archive/2008/11/25/working-with-large-models-in-entity-framework-part-2.aspx#10159696</link><pubDate>Sat, 30 Apr 2011 06:44:04 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10159696</guid><dc:creator>MSanaei</dc:creator><description>&lt;p&gt;any answer?&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10159696" width="1" height="1"&gt;</description></item><item><title>re: Working With Large Models In Entity Framework – Part 2</title><link>http://blogs.msdn.com/b/adonet/archive/2008/11/25/working-with-large-models-in-entity-framework-part-2.aspx#10158635</link><pubDate>Wed, 27 Apr 2011 14:43:53 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10158635</guid><dc:creator>MSanaei</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;I don&amp;#39;t understand in multiple schema set method, How &amp;quot;customerdetails.model.cs&amp;quot; created? could you help me? whats it&amp;#39;s command?&lt;/p&gt;
&lt;p&gt;and&lt;/p&gt;
&lt;p&gt;how can i use these files in my project? I copy that files in a directory and change my connectionStrings in app.config to refer to that files,but this cause my project generate 49 errors!&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10158635" width="1" height="1"&gt;</description></item><item><title>re: Working With Large Models In Entity Framework – Part 2</title><link>http://blogs.msdn.com/b/adonet/archive/2008/11/25/working-with-large-models-in-entity-framework-part-2.aspx#10122241</link><pubDate>Mon, 31 Jan 2011 10:23:19 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10122241</guid><dc:creator>Neel</dc:creator><description>&lt;p&gt;I am using T4 template to generate POCO Classes which are then moved to another project. Can you please provide some tips as to how can we divide the EF model into separate models while using POCO Classes ?&lt;/p&gt;
&lt;p&gt;thanks in advance&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10122241" width="1" height="1"&gt;</description></item><item><title>re: Working With Large Models In Entity Framework – Part 2</title><link>http://blogs.msdn.com/b/adonet/archive/2008/11/25/working-with-large-models-in-entity-framework-part-2.aspx#10121279</link><pubDate>Thu, 27 Jan 2011 23:50:57 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10121279</guid><dc:creator>getting sick by this blog</dc:creator><description>&lt;p&gt;have you tried this in EF4.0, at least once, based on your defined steps in the blog.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10121279" width="1" height="1"&gt;</description></item><item><title>re: Working With Large Models In Entity Framework – Part 2</title><link>http://blogs.msdn.com/b/adonet/archive/2008/11/25/working-with-large-models-in-entity-framework-part-2.aspx#9913609</link><pubDate>Tue, 27 Oct 2009 18:04:01 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9913609</guid><dc:creator>Adam</dc:creator><description>&lt;p&gt;Will any of the &amp;quot;large model&amp;quot; issues mentioned in Part I and Part II be addressed in the upcoming EF4 release? &amp;nbsp;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? &amp;nbsp;Or at least if there will be a less manual approach to splitting models in EF4? &amp;nbsp;&lt;/p&gt;
&lt;p&gt;My team is in the process of migrating an application with LOTS of tables. &amp;nbsp;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. &amp;nbsp;Unfortunately we couldn't add all of the tables to EF due to performance problems and others issues mentioned in these blog posts.&lt;/p&gt;
&lt;p&gt;Thanks in advance for any information you can provide!&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9913609" width="1" height="1"&gt;</description></item><item><title>re: Working With Large Models In Entity Framework – Part 2</title><link>http://blogs.msdn.com/b/adonet/archive/2008/11/25/working-with-large-models-in-entity-framework-part-2.aspx#9910546</link><pubDate>Wed, 21 Oct 2009 12:59:25 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9910546</guid><dc:creator>Tooraj</dc:creator><description>&lt;p&gt;Hi Srikanth,&lt;/p&gt;
&lt;p&gt;Is there any fix for the &amp;quot;large model&amp;quot; issue in version 4?&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9910546" width="1" height="1"&gt;</description></item><item><title>re: Working With Large Models In Entity Framework – Part 2</title><link>http://blogs.msdn.com/b/adonet/archive/2008/11/25/working-with-large-models-in-entity-framework-part-2.aspx#9910194</link><pubDate>Tue, 20 Oct 2009 21:03:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9910194</guid><dc:creator>Koistya `Navin</dc:creator><description>&lt;p&gt;Having one .edmx file might be good as far as it could be easily edited both manually and via designer.&lt;/p&gt;
&lt;p&gt; - For the manual editing improvements you could add one simple feature which will provide some sort of &amp;quot;navigation links&amp;quot;. 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.&lt;/p&gt;
&lt;p&gt;- 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 &amp;quot;aggrigates&amp;quot;. Zoom in/out int0 aggrigates view and into entities view.&lt;/p&gt;
&lt;p&gt;-- &lt;/p&gt;
&lt;p&gt;navin@php.net&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9910194" width="1" height="1"&gt;</description></item><item><title>re: Working With Large Models In Entity Framework – Part 2</title><link>http://blogs.msdn.com/b/adonet/archive/2008/11/25/working-with-large-models-in-entity-framework-part-2.aspx#9863169</link><pubDate>Mon, 10 Aug 2009 16:19:30 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9863169</guid><dc:creator>Dhileep</dc:creator><description>&lt;p&gt;By the way, I used your option B to create 2 sets of csdl, msl and ssdl files for the models and used &amp;quot;using&amp;quot; in the second model to refer the entities in the first model.&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Dhileep&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9863169" width="1" height="1"&gt;</description></item><item><title>re: Working With Large Models In Entity Framework – Part 2</title><link>http://blogs.msdn.com/b/adonet/archive/2008/11/25/working-with-large-models-in-entity-framework-part-2.aspx#9863167</link><pubDate>Mon, 10 Aug 2009 16:16:48 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9863167</guid><dc:creator>Dhileep</dc:creator><description>&lt;p&gt;Hi Srikanth,&lt;/p&gt;
&lt;p&gt;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 &lt;/p&gt;
&lt;p&gt;&amp;quot;System.InvalidOperationException: The relationship 'DataAccess.EF.ParameterListValuesParameters' does not match any relationship defined in the conceptual model&amp;quot;. &lt;/p&gt;
&lt;p&gt;Do you have idea about this error? &amp;nbsp;I searched in net for this error but no help.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9863167" width="1" height="1"&gt;</description></item></channel></rss>