>>
>>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...

** Update **

So from what Mike posted I infer that you are not "condemning" EF altogether, but just it's code-first flavour?

** end update **

So I'm curious, so you're supposed to name all your sql's however tiny right as they will be processed via stored procedure? How do you organize that in terms of naming strategy?