Re: does Query Optimizer reach beyond the LIBL to find access paths?

I often made use of this fact when digging into SQL performance issues in
production...

I couldn't create objects in the production libraries. But I could create
indexes in my own personal library over production tables in production
libraries.

This allowed me to see what effect they would have on particular queries
before going to our change management process to make them permanent.

Charles



On Thu, Dec 14, 2023 at 2:34 PM Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:

Yes indeed.

In fact, the DB can always use an access path, regardless of the library
or authorities on on object.

Charles

On Thu, Dec 14, 2023 at 2:30 PM Musselman Paul via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

A question arose with WebQuery queries written using views in a library
NOT in the LIBL.
Does the Optimizer user whatever access path it can see (attached to the
physical file), even if not in the LIBL?


[cid:image001.png@01DA2EAA.D5795E70]
_________________________________________________
If you have a support issue, please Submit a ServiceNow Ticket<
https://prysmiansd.service-now.com/sp/>

Paul E Musselman
Sr. Technical Support Analyst
IT Power Systems
North America Information Technology
[cid:image002.png@01DA2EAA.D5795E70]
Cell + 1 859 953 3134
Email: paul.musselman@xxxxxxxxxxxxxxxxx<mailto:
paul.musselman@xxxxxxxxxxxxxxxxx>
4 Tesseneer Drive
Highland Heights, KY 41076
United States



Confidentiality Notice - This message and its attachments (if any) may
contain confidential, proprietary or legally privileged information and

it

is intended only for the use of the addressee named above. No
confidentiality or privilege is waived or lost by any mistransmission.

All

reply messages and/or all attachments included, and transmitted incoming
and/or outcoming from/to the Prysmian Company could be know from its .

If

you are not the intended recipient of this message you are hereby

notified

that you must not use, disseminate, copy it in any form or take any

action

in reliance on it. If you have received this message in error, please,
delete it (and any copies of it) and kindly inform the sender, of this
e-mail, by replying or go to Prysmian site on "contact us". /// Le
informazioni contenute nella comunicazione che precede possono essere
riservate e confidenziali e sono, comunque, destinate esclusivamente

alla

persona o all'ente sopraindicati. La confidenzialit?, sicurezza e
la correttezza dei messaggi di posta elettronica non possono essere
garantite. Prysmian potrebbe avere nozione di tutti i messaggi di

risposta

e/o tutti gli allegati, alla/dalla stessa trasmessi e/o ricevuti.

Qualora

Lei non fosse la persona alla quale il presente messaggio ? destinato,

la

invitiamo a non procedere ad alcun uso, distribuzione, copiatura od

azione

ad esso conseguente. Se avete ricevuto questo messaggio per errore La
invitiamo ad eliminarlo dandocene gentilmente comunicazione rispondendo

a

questo messaggio oppure attraverso il "contact us" sul sito web Prysmian
site.
--
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.

--
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.