|
I have had co-workers run poorly constructed query/400 (e.g. join inventory history file's millions of records with cost master's 1/2 million records) on-line, and bring the 400 to its knees. I show the culprit how to run that on JOBQ, then they do same thing again, acting like the 400 to its knees is some glitch they have nothing to do with.
Are there any performance issues to consider when looking at embedded SQL versus Query400? It seems that Query400 might actually run faster, but I can definitely see the advantages of creating an SQL statement on the fly per se. Thoughts, comments? Tell me I'm nuts....ok skip the last one, that's a given. If you bought it, it was hauled by a truck - somewhere, sometime. -- 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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.
midrange.com
