Performance optimisation hell
As a DBA, I loathe Entity Framework (and ORMs in general)
I see it as time stolen from the DBAs so that the developers can meet their deadlines.
EF is performance optimisation hell. SQL Server keeps nice data about what objects are run, how often, what execution plans they use and so on.
If stored procedures have become resource hogs or taking their sweet bloody time to execute, SQL Server provides the data for me to react.
But with EF I get these long ugly chunks of SQL that I have to dissect. And even then, it can't be guaranteed that the next execution of the same EF code will result in the same SQL. So when someone from Helpdesk or a PM says that the x functionality is running slow, I can look at the SQL and hold my head and sigh.
Running baselines for objects is doable with SPs but not really with EF.
It all has to go back to the developers, which means that the problem won't be solved until another couple of sprints.
At least with SPs I can test the code in the object, optimise in and submit it in a sprint myself