Has anyone found a good workaround to the following linq-to-sql eager loading issues? http://www.lowendahl.net/showShout.aspx?id=190 I'm experiencing a similar issue where when trying to get back an object graph deeper than one level linq-to-sql generates an enormous number of round trips to the DB in order to handle a situation similar to this:
Grand Parent
--Parent
----Child
The above relationship could easily be generated in one sql call, but linq-to-sql generates multiple round-trips to build up the relationship. Does anyone have a good work around for this?