|
Birgitta Hauser wrote on 06/12/2006 12:58:36 AM:
When concatenating several fields no indexes can be used, because a
"new"
field is created and indexes only can be used for existing fields. But using GROUP BY may cause ALL rows being. Using DISTINCT may be the better solution, because it can work as SETGT/READ in RPG. And if there
is
an index that consists only of the selected fields an IOA (index only
access
= the fastest way to access data, because all necessary information is
in
the key and no additional access to the rest of the row is necessary)
can be
performed.
Thanks Birgitta, that is the kind of thing I'm interested in learning about. From now on I'll definitely be trying to think "could I use DISTINCT instead?" when I'm doing a GROUP BY. Thanks again, Adam ##################################################################################### Attention: The above message and/or attachment(s) is private and confidential and is intended only for the people for which it is addressed. If you are not named in the address fields, ignore the contents and delete all the material. Thank you. Have a nice day. For more information on email virus scanning, security and content management, please contact administrator@xxxxxxxxxxxx #####################################################################################
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.