|
Hello,
I hope someone can point me in the right direction to help us debug some
SQL run-time inconsistencies.
We have some SQL queries, that access the IBM i DB2 database, that have
wildly different run-times depending on the client. We can run the
queries from the Surveyor product and it runs consistently time-wise
each time. This is true if we run the queries in the IBM ACS SQL
client. If we run that same query from within a product called
FileMaker the run-times will be wildly inconsistent and usually much
much much longer. Although, there are times when it matches the
Surveyor run-times.
The FileMaker product is connecting to the IBM i via the ODBC driver
from IBM ACS.
We have just started developing these queries so it isn't a case of "it
was working fine and now it isn't".
Where should I start looking to figure this out? What are the most
likely culprits?
Any help will be appreciated.
Thanks and regards,
Bobby
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
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.