>>
>>I would recommend looking at the Code-First methodology and getting familiar with EF Migrations.
>
>Why ? in the bigger gigs that is a no-no over here. DB first and DBA has aways last word...

Yeah, that is an issue. You really have to buy into the "the DB is a place to persist data, and only a place to persist data" idea. It's an agile idea and it's taken me several years to actually buy into it, but now that I have I don't want to go back. :-)

Although you're not completely taking the DBA out of the equation. You are still generating a database. You do have configuration options in EF so you can customize the schema. It's just a different workflow - you don't make changes directly to the DB (which arguably you shouldn't be doing anyway).