topic Re: SQLM missing results Current vs Time Interval in Application Development and Automation Discussions

SQLM missing results Current vs Time Interval

Szczerbowski — Fri, 10 Mar 2023 12:35:53 GMT

Hi,

I had SQLM running in production for a couple of days and I found out one of the top consumers to be a report that we thought was decommissioned, in the entry points it says it's a Batch job but I cannot find that in SM37 log.I

It only shows in the result list if I select Current Data, and not if I select by Time Interval.

I was running my SQL log 14-17Feb, and if I select this as time interval, the entries won't show, if I select Current - it's there. Also..

I ran SQLM in my QA too last week, to try to find this job there, and again if I select by Time interval 7-10 March, this report is not listed, but if I select Current Data it is there - AND IT HAS exactly the same execution count as in production! 51 656 211 executions.

So is this some ghost execution count that did not really happen or where does it come from?

Regards,
Michal

Re: SQLM missing results Current vs Time Interval

fedaros — Sat, 11 Mar 2023 10:37:43 GMT

Hi Michael,

See the following usage scenario for further information on how SQLM's results are persistent and how you may view results from all servers in one instance, this explain the "ghost":

https://help.sap.com/docs/SAP_NETWEAVER_AS_ABAP_FOR_SOH_740/a24970c68fcf4770a64bf9a78e3719e2/1ec2329419b64f3992a9c342437d3a0f.html

Related to not found it on SM37, I guess despite to see request type as Batch Job, the report information is Request Entry Point, which is related to SQL and not batch job.

https://help.sap.com/docs/SAP_NETWEAVER_AS_ABAP_FOR_SOH_740/a24970c68fcf4770a64bf9a78e3719e2/5ad2f48682bb48bd81bf332ff7585823.html#loio5ad2f48682bb48bd81bf332ff7585823

Regards, Fernando Da Rós

Re: SQLM missing results Current vs Time Interval

Szczerbowski — Mon, 13 Mar 2023 08:00:43 GMT

Thanks for help,

So if I read this correctly..

I checked the activation log and I can see that SQLM was running in our production system in 2018 for a couple of days, then that DPR_.. report would make sense. Then if I select Current, it mixes up those two timeframes old and new. And if I select that activation week in Feb 2023, then of course it's not there.

Also, why QA has exactly the same results, because we did a system refresh some years back, then it would probably also copy sqlm results, and they show up with exactly the same values as in prod.

Makes sense in a way. Weird I cannot display data for that other week in 2018 as it says no data found, but I guess there is an expiration date on results if I don't snapshot them.

Regards,
Michal