>>>>To be fair, most of the SQL generated from EF is strange.
>>>
>>>Generally that's been the case with other tools. The code in LINQ to SQL was never optimal. The code generator in SSRS generates some very bizarre code against OLAP cubes.
>>
>>NHibernate's SQL was always more straightforward to the point where 80% of the NH queries generated SQL similar or better than what I would write manually and the rest of the 20% could be optimized to a satisfactory point with a little elbow grease.
>>
>>EF's is different. Their Migrations functionality is awesome (there are some issues in a team environment though), but EF in general seems slightly below par. It's driving me in the NoSQL direction but I'm not quite there yet. RavenDB might be my next venture as the developer is the same as NH and he's got a lot of the same opinions as I do.
>
>True on NHiberate. And remember where it came from :) There's a reason it didn't have a reputation for generating really bloated code. :)
>
>I've come to realize NoSQL has its place.

Yes, most of the projects I work on would have development times greatly reduced by embracing NoSQL. Unfortunately not everybody I work with has come to the realization that you have. Building tables, fields, setting data types, setting indexes, configuring keys, blah blah blah is familiar and gives a sense of accomplishment; unfortunately, the original goal was to create useful software and not the perfect database.