Hash Table Probe -- MIDRANGE-L

Subject: Hash Table Probe
From: Greg Wilburn <gwilburn@xxxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 17 Jun 2020 15:10:17 +0000
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

I have and SQL COUNT statement running over a complex SQL View... The SELECT statement of the same rows takes 1-2 seconds. The COUNT(*) takes 6-8 seconds.

When I ran this through RUN SQL SCRIPTS using run & explain, I see:
Hash Probe <- Temporary Hash Table <- Table Probe

The Table Probe is 90% of the time used. I'm just not sure how to eliminate or reduce the amount of CPU time this takes.
I already have quite a few indexes over the DB2 table... I can see that in the "List of Indexes Optimized"

Anyone point me in the right direction?

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Hash Table Probe , Charles Wilt
Re: Hash Table Probe , Nathan Andelin

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.