Index over QSYS/QADBXREF -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Index over QSYS/QADBXREF
From: Justin Taylor <jtaylor.0ab@xxxxxxxxx>
Date: Fri, 9 Sep 2022 09:19:30 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
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>

VE is recommending an index over QSYS/QADBXREF. The query in question is
using QSYS2.RECORD_LOCK_INFO. I've never seen an index recommended over a
QSYS table before. Is it a bad idea to create indexes over QSYS tables
(they'd be in a diff schema of course).

TIA

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Index over QSYS/QADBXREF , Mark Waterbury
Re: Index over QSYS/QADBXREF , MidrangeL

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.