•Clean initial SQL, written by a
developer who fully understands the functional requirements, is likely
to get a good execution plan from the optimizer without manual
tuning.
•Even if clean initial SQL does not
perform well, as a clean, transparent, correct spec for the functional
requirements of the application, it is much easier to tune
than unclean SQL, and it avoids wasting time tuning something
that isn’t even functionally sensible.