<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://msmvps.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>How to split your EDM?</title><link>http://msmvps.com/blogs/matthieu/archive/2009/05/27/how-to-split-your-edm.aspx</link><description>One of my customers wants to code an ERP. To make it, he wants to use EF. His DB has more than 600 tables with a lot of relationships between all of them. The problem is the fact that Entity Framework has some difficulties with big models. You should</description><dc:language>en</dc:language><generator>CommunityServer 2008.5 SP2 (Build: 40407.4157)</generator><item><title>Working with Large Databases in Entity Framework</title><link>http://msmvps.com/blogs/matthieu/archive/2009/05/27/how-to-split-your-edm.aspx#1739503</link><pubDate>Fri, 13 Nov 2009 12:32:54 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:1739503</guid><dc:creator>Gil Fink on .Net</dc:creator><description>&lt;p&gt;Working with Large Databases in Entity Framework Yesterday I was asked by a colleague a very good EF&lt;/p&gt;
&lt;img src="http://msmvps.com/aggbug.aspx?PostID=1739503" width="1" height="1"&gt;</description></item></channel></rss>