I was also looking for an answer. Turns out there is a pretty great way to view the EF generated SQL code if you don't mind plunging into the somewhat sketchy world of reflection.
A very resourceful poster on the MSDN forums wrote a set of extension methods that allow you to unload SQL output from an ObjectContext (i.e. the material that will be executed when SaveChanges() called).
You can find the link here - find the g_yordanov message containing the CustomExtensions class.
I tested this in the last little time, and it seems like a pretty trick. The only catch was that I had to make the correction suggested by David Cater in this thread - changing the Dictionary<long, object> to Dictionary<int, object> .
Marty dill
source share