On run it, that is what I have been doing, having set the logging level and making sure cacheing was off, and then looking at it via diagnostics expecting too see logical and physical sql, but in fact only seeing logical sql,
From you saying 'jokes aside' I assume that the original way should facilitate viewing the sql, yes?
I need to work on my humour...
My point is that if you want to get the (or all) physical SQL statement(s) without actually having to run things in the front-end and then extracting the statement from the logs or copy/pasting it from "Manage Sessions" then you can script it via nqcmd.
but I am running it and I am not seeing physical SQL when I use; -
1. Create diagnostic sql view in the report
2. Set logging level 5 and view diagnostics log via manage sessions
Is this a change in 12.2.1 that you have to use the NQCMD?!
Apologies if I am being less than crystal clear.
What all information you are getting in your Administration-->Manage Session-->Session Log once you have set Log Level 5 at Report-->Advanced Tab-->Prefix section, do you see in your Report Session Log whether logs start as SET VARIABLE QUERY_SRC_CD='Report',LOGLEVEL=5 ....., you should see this piece of information if log level has been set at report level.
There's a bug in 184.108.40.206 that affects logging (Doc ID 2175402.1).
As a workaround, you can try enter the following parameters in the Advanced tab -> Prefix box
SET VARIABLE LOGLEVEL=2,DISABLE_CACHE_HIT=1;
After you run the analysis, you can view logs to see it.
Many thanks, that is what I was looking for.
love the way upgrades result in functionality that worked previously n longer working as standard!
Next time say that you're on 220.127.116.11.0 right away - it'll help to identify the issue much faster.
Also: That version is out of error correction support as of this month since it's already more than 18 months old. High time to upgrade