>>Whenever you need nearly unfiltered outer joins and execute them server side, chances are the result set sent over the wire is larger than the tables it was generated from - and Left Joins do turn up in biz settings. Full Join could be oodles worse, but I confess I cannot remember last time I needed one, so that would be straw man argument / just for the sake of making a point ;-)
>
>Sure but bad SQL is bad SQL.

Yupp, but Al's point was on code written not to best practices.

One will gain by using C/S responsibly, but often the move to SQL backend with all queries done then on backend is painted as the silver bullet costing not even copper prices (just port the data at relatively easy to calculate cost...) without even thinking of underlying HW and data size best practices

>You'll have the same issue in network disk access, unless you don't use SQL in the first place (ie. SCAN or Indexed lookups) - but then if you do that you likely could do the same in SQL or pull multiple non-joined tables and locally join them or lookup as needed.

Yupp, that in my book is needed to be considered best practice, but all to often such tweaks are not mentioned when decision and cost of moving is discussed...

regards
thomas