Maybe some trashing of MTI ??
have a look
SELECT TABLE_SCHEMA, TABLE_NAME, LEADING_COLUMN_KEYS,
KEY_COLUMNS_ADVISED, MTI_USED, MTI_CREATED, LAST_MTI_USED
FROM QSYS2.SYSIXADV
WHERE MTI_USED > 0 OR MTI_CREATED > 0
ORDER BY MTI_USED DESC
OR MAYBE BETTER
SELECT * FROM TABLE(QSYS2.MTI_INFO('*ALL', '*ALL'))
ciao
..
On Wednesday, May 27, 2026 at 07:42:19 PM GMT+2, Greg Wilburn <gwilburn@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
I have a relatively complicated database view that references other views. Back in 2020, I was able to create some indexes to improve performance when this view was used.
Without going into a lot of detail, I added a column to the view to simply count the lines in the primary table (the view already groups results). I did this generating the DDL from ACS Schemas tool. Using run sql scripts, I did a "create or replace view" after adding the column. This change killed the performance, so I removed the new column and ran "create or replace view" again.
Now to the odd part... the performance was still horrible. I didn't know what to do, so I restored the view from our cloud backup - this fixed the performance issue.
My question is why? What is happening behind the scene that I'm not considering?
I honestly can't imagine that adding a "count(myfield) as mynewfield" column would dramatically affect the performance.
Greg
[Logo]<
https://www.totalbizfulfillment.com/> Greg Wilburn
Director of IT
301.895.3792 ext. 1231
301.895.3895 direct
gwilburn@xxxxxxxxxxxxxxxxxxxxxxx<mailto:gwilburn@xxxxxxxxxxxxxxxxxxxxxxx>
1 Corporate Dr
Grantsville, MD 21536
www.totalbizfulfillment.com<
http://www.totalbizfulfillment.com>
midrange.com
