title: What to use with a half-designed database? Model-First or Database-First?
body: <p>Let's say you have a database that is currently in use. It has one table that contains some information about <code>Customers</code>.</p>
  
  <p>And let's say that you want to create an application around it. You need to use the <code>Customers</code> table in your program, but you also need to add some new tables, possibly connected to the <code>Customers</code>. For example, you need to add an <code>Orders</code> table that has some association to the <code>Customers</code> table.</p>
  
  <p>I have started to learn Entity Framework. I have learned a bit about "Database-First" and "Model-First" data models. But the situation is, what I want to do doesn't fit into any of these categories. I neither have a completely empty database, nor a finished database schema that can directly be used in the program.</p>
  
  <p>What should I do? If I go with "Model-First" and design my entities using the Visual Studio Designer, can I just use it to create the relevant part of the database schema?</p>