Hello Anna,
I need to preface by saying that the loggers that I will provide are VERY VERBOSE, so we usually advise to prepare as much as possible the reproduction path and to limit as much as possible the actions/number of clicks, once the configuration updated.
Now, that being said, here are the loggers to update in the logging configuration module:
<Logger level="DEBUG" name="org.springframework.jdbc.core.JdbcTemplate"/>
<Logger level="TRACE" name="org.springframework.jdbc.core.StatementCreatorUtils"/>
The 1st one will log all SQL queries executed from MDM apps.
And the 2nd one will log the parameters set in prepared statements.
Please note to also adjust the root level to TRACE.
Once you've caught the query, you can then strive to identify the possible enhancements and/or optimizations to be done (indexes for example). Doing an explain plan (an "explain (analyze, buffers, timing)" brings even more information) can always help to bring detailed information to your DBA for assistance.
Anna
My goal is to improve performance in the data steward application. It takes 1-2 minutes to open a Duplicate Management "workflow" even though I only checked out about 7 golden records (and the golden records typically don't have more than 10-15 master records maximum attached to the golden).
I'm not able to open the UI to confirm golden records or if the duplicate manager finally opens, it can take more than 5 minutes for the screen to update.
I need to troubleshoot how to fix the performance issues. What are the best practices for benchmarking the performance on Day 1?
I remember there are some logging configurations I can make to track the load/process time for measuring the data steward application. Can you please share the logging config?
Thanks in advance.