As an experienced ADO.NET/TSQL developer, it's been my experience on every project that has used EF, headaches and issues have arisen during maintenance and while attempting changes. For years, I thought perhaps it's because EF wasn't properly implemented in the first place. I mean, who doesn't enjoy generated data entity class objects, etc... After readying quite a bit of negativity on using ORM's instead of stored procedures, it's obvious that the opposite of rational knowledge is one's intuition, or gut feeling... Thus, I feel slightly vindicated but should have listened to my instinct all along.. :)