title: Using Code-first Entity Framework to add new tables to large, existing database which is consumed by non-EF applications
body: <p>I'm writing a small application which requires ~6 new tables to be added to a large database (~100 tables). My application is not interested in any of the existing tables or DB structure, indeed it's likely my new tables will all be in a new schema.</p>
  
  <p>Other people will be writing stored procedures to access my new tables so I can't see them being happy without a DDL to refer to. I'm new to EF but because these tables have a lot of fields it seems a good option to avoid manually creating the DDL.</p>
  
  <p>What is the best option here? I'm wondering if I should use EF anyway but just as a way to spit out a DDL using annotations? I'm brand new to EF so please assume little knowledge if you start talking about migrations, etc!</p>