>We're having a debate about whether to use EF AddOrUpdate.
>
>According to Julie Lerman at http://thedatafarm.com/data-access/take-care-with-ef-4-3-addorupdate-method/ you should only use AddOrUpdate when doing Data Migrations during development.
>
>My co-workers are saying that using AddOrUpdate is acceptable even though it makes a round trip query to the database to see if the record exists in order to determine whether it creates an update or an insert command. I've seen that in SQL Profiler.
>
>And Julie makes other arguments against its use as well.
>
>Thanks.

I was about to reply with the same thing that Naomi said. The MERGE statement in SQL 2008 (plus the ability to pass data tables as parameters to stored procs) gives you more power in the database engine. There are strong arguments to do this in the database layer.