|
Hi,
Beware, I'm in deep water and may have misunderstood most of what I'm
trying
to explain below:
Trying to analyze a bunch of ODBC requests for performance improvements and
my starting point is to compare where-clauses to available indexes.
Found a schema with a bunch of large tables - and to my surprise NO
indexes.
DSPLIB - no. DSPDBR - no. Went graphical at
:2001/Databases/Schemas/Schema/Indexes - no.
However I found a bunch of constraints named Q_* that can be found at
2001:/ Databases/Schemas/Schema/Tables/Table-right-click/Show indexes.
It seems to me that the SQL manager creates an index for every constraint
being defined and if I run an sql-statement in Visual Explain it actually
uses the Q_* index.
Questions:
Anyone knows the reason those indexes are not showed up as indexes unless I
right click on the specific table name and click Show Indexes?
Why are they hidden? I can't get usage information etc.
If I'm reasonably right about these indexes being used it seems appropriate
to add a lookup to qsys2.syskeycst in my DB relations analyze program.
If I'm going to loose more hair on this I probably have to start with arms
and legs..
Thanks!
Stefan
--
Stefan Tageson
Mobile +46 732 369934
--
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@xxxxxxxxxxxxxxxxxxxx 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-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.