>I think that's often the case, but from what I hear, EF does a pretty good job.
>
>But keep in mind, ORM is not designed for not should it replace all data access. It designed to handle 80-90% of standard CRUD operations.
>
>>According to an article by Julie Lerman in MSDN Magazine last year, the ORM tools can generate some horribly inefficient SQL. I don't know whether that's true or how frequently it happens but that's what she wrote.

It is very true, at least from what I've seen watching EF work through SQL Profiler.

Last I dealt with it (a couple of years ago and maybe it has dramatically improved since) I was astounded at the sheer number of calls to the database being done for what should be simple single statement commands.

That combined with having to manually add Stored Procedure code in multiple places after each generation of the EF code put me right back to doing things the simple way (at least after I got away from Silverlight).

Maybe I'm just not looking at it correctly (but I was looking at profiler correctly).