Question
Tata Consultancy Services Australia
PH
Last activity: 10 Oct 2017 5:55 EDT
Multiple DB calls in a strategy
Hi Team,
Do you know of a way to get rid of multiple RDB-Open in a strategy? We've implemented this to get a count(*) of some value from the database for each of the propositions.
Thanks,
Pegasystems Inc.
AU
Hi,
Could you please elaborate more on the query?
It would be helpful if you could share more details on your investigation, which identified multiple RDB-Open for a Strategy. Along with relevant screen-print of the strategy canvas fetching the count(*) for propositions.
Thanks,
Santhosh
Pegasystems Inc.
NL
Hi,
Could you please share the details of your strategy and the generated SQL? In general, the SQL generated for strategies (from IH import) is optimized. I'd like to understand what the issue is exactly.
To trace the queries, use the Pega tracer. Disable all "Events to trace", enable just DB Query as "Event types to trace". Select just the Pega-DecisionEngine and Pega-DecisionArchitect rulesets.
Hi,
Could you please share the details of your strategy and the generated SQL? In general, the SQL generated for strategies (from IH import) is optimized. I'd like to understand what the issue is exactly.
To trace the queries, use the Pega tracer. Disable all "Events to trace", enable just DB Query as "Event types to trace". Select just the Pega-DecisionEngine and Pega-DecisionArchitect rulesets.
You'll be getting something like:
Or, formatted
Note that there are many variations of the generated SQL, depending on select conditions, filters, whether or not there are multiple IH retrieval operations etc.
If you could share this on this thread along with the (relevant) strategy components, that will help us understand the issue (if any) better.
Thanks
Otto