title: C# Entity Framework DBContext
body: <p>I am trying to learn Code First EF6 and I am confused regarding DBContext.</p>
  
  <p>The database I will be working on contains 800+ tables, while when working of specific parts of the application I am only dealing with 1-10 tables.</p>
  
  <p>So my question is; would not having a DBContext involving 800+ Classes have a big negative impact on system resources?</p>
  
  <p>I guess I am new to this technology and confused regarding the actual meaning of the information that I am taking in during my research.</p>
  
  <p>Thank you.</p>
  
  <p>NOTE: Thank you for your inputs. Please take a look at this post: <a href="https://stackoverflow.com/questions/20551236/using-multiple-dbcontexts-with-a-generic-repository-and-unit-of-work">Using multiple DbContexts with a generic repository and unit of work</a>. There it states I cannot have tables in separate contexts that relate to each other?!</p>
  
  <p>But in a real world scenerio my understanding is that it is common to break up the table relationships in focused areas, how is this done in Code First EF? Thanks again.</p>