title: Can a project have two different EF data models that reference the same table?
body: <p>I've system that has a primary data model to perform most of the work. </p>
  
  <p>The model has quite a few tables and with <a href="http://www.codeproject.com/Articles/38922/Performance-and-the-Entity-Framework" rel="nofollow noreferrer">performance in mind</a> when I came to add an administrative feature to the application I decided to use a second separate data model. </p>
  
  <p>All works well until my second data model needs to access a table that is also in the primary data model. Now, from digging around I can see <a href="https://stackoverflow.com/questions/4761201/ef4-two-models-one-database-possible">this can cause problems</a>.</p>
  
  <p>The two possible workaround I've come up with are to either:</p>
  
  <ol>
  <li>Put the data models in separate projects.</li>
  <li>Use views / stored procedures for accessing the table in question when required.</li>
  </ol>
  
  <p>Method 1 seems the simpliest but I'm concerned about whether there would be any performance loss. Method 2 seems a bit messy and takes the point out of using EF.</p>
  
  <p>Before I plump for using method 1, is there an easier work around that I could use?</p>