As a developer I've seen some truely awful SQL. Is LINQ going to make that better or worse? Personally I think it'll make the problem even worse.

In most environments I've worked in the DB has always been the key to good performance. If there is a complex data object hierarchy, which is where LINQ is supposed to be the timesaver, it will need competent and efficient SQL to access it. And who here honestly thinks LINQ will be generating competent and efficient SQL?

LINQ is the DBA and professional developer's worst nightmare. It muddles the clear distinction between a relational data orientated layout and an object orientated layout. Knowing and understanding that relationship is often where good programming for performance lies.