• As an experienced app developer and DBA, I have the following thoughts:

    Selecting data within Entity framework using Stored Procs is somewhat of a nightmare for devs. Selecting data through the entity model often generates huge SQL statements which are often made of case statements to determine which part is actually executed on the SQL Server or use a massive amount of unnecessary sub queries. These generate many execution plans on the SQL server, rarely reusing a current execution plan. This is a nasty performance hit on the SQL box. It takes away scope from the DBA to rejiggle SQL code to provide a better execution plan. It leaves the DBA only with option of looking at cached plans on the server and generating any necessary indexes which is only "half a job". It also bloats SQL log files from the somewhat crazy SQL statments that Entity Framework generates to execute against the SQL Box. The product is of complete dismay to me. If you want to have a performant SQL Server and work in an enterprise environment my advise (and I talk from experience) is to stay away from Entity framework!