my bad, I misread which one you said was running slower.


Michael Schutte
Admin Professional





midrange-l-bounces@xxxxxxxxxxxx wrote on 03/18/2008 03:31:32 PM:

cuz there's not as much data being requested.

You could get even more speed if you remove the where clause and put it
in
the JOIN...

ON ODORD# = OLORD#
AND ODLINE = OLLINE
AND OLSTTS <> ODSTTS



Michael Schutte
Admin Professional
Bob Evans Farms, Inc.



midrange-l-bounces@xxxxxxxxxxxx wrote on 03/18/2008 03:22:11 PM:

Why would the last of the following two SQL statements run ten times
slower than the other?


SELECT *
FROM BLORDLP A
JOIN BLORDDP B
ON ODORD# = OLORD#
AND ODLINE = OLLINE
WHERE OLSTTS <> ODSTTS


SELECT ODORD#, ODLINE, ODSTTS, OLSTTS
FROM BLORDLP A
JOIN BLORDDP B
ON ODORD# = OLORD#
AND ODLINE = OLLINE
WHERE OLSTTS <> ODSTTS

The only difference being the first selects all fields and runs
immediately, the second only selects 4 fields and takes forever to
run.

thanks,

rick
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].