SQLM is not considering all the 'select *' error c...
Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
When I am trying to run SQLM for Z* package in my development system. Its giving only few Select query errors and not all. Is it because SQLM picks only specific select queries or because I am using it in Development system?
When I am trying to run SQLM for Z* package in my development system. Its giving only few Select query errors and not all. Is it because SQLM picks only specific select queries or because I am using it in Development system?
the SQLM shows the captured SQL profile, so assume you have report A and B, you activate the SQL Monitor but you only execute report A. After deactivation you investigate the results, so you won't see report B in the SQL Monitor data, as it has not been executed.
Therefore, it's important to regularly repeat the measurements with the SQLM, as you might lack certain business processes, which are not accessed in the phase when the SQLM has been activated. One example is year-end reporting, which would be missing in the SQLM data, if you don't activate the SQLM during these reporting periods.
Thanks for the reply, I followed the same procedure but after deactivating SQLM, when I tried to run it, It gives me the same old output and not the new trace.
First, I activated the monitor then Ran all the programs, then after deactivation I checked again and it was giving the same old output and not the new trace with new programs.
you might need to update the statistics, i.e. the data is send asynchronously for storage. To trigger that manually, you can go to transaction SQLM and select (from the menu) something like SQLMonitor > Refresh.
Bluesky
