Question
Last activity: 19 May 2016 11:50 EDT
Mystery query to pr4_rule_vw that does not show up on a global db trace
MSSQL DBA reports a query that runs periodically and takes a long time in the DB. The query takes very little time when run from MSSQL tools.
Checked SendStringParametersAsUnicode - that seems fine.
Went looking in alerts and could not find the query.
Enabled global db trace for a bit. Could not find it
What is this?
SELECT pyClass AS "pyClass" , pxInsName AS "pxInsName" , pyRuleSet AS "pyRuleSet" , pyRuleSetVersion AS "pyRuleSetVersion" , pxUpdateDateTime AS "pxUpdateDateTime" , pyLabel AS "pyLabel" , pyRuleName AS "pyRuleName" , pyClassName AS "pyClassName" , pyRuleAvailable AS "pyRuleAvailable" , pyCircumstanceProp AS "pyCircumstanceProp" , pyCircumstanceVal AS "pyCircumstanceVal" , pyCircumstanceDateProp AS "pyCircumstanceDateProp" , pyCircumstanceDate AS "pyCircumstanceDate" , pyRuleStarts AS "pyRuleStarts" , pyRuleEnds AS "pyRuleEnds", pxInsName as "pxInsHandle" FROM Rules.pr4_rule_vw WHERE pxObjClass = 'Data-Rule-Summary' AND ( ( pxInsName LIKE '%LOCALREQUIREMENTS%' ) AND ( pyClass NOT LIKE 'Rule-AutoTest%' ) ) ORDER BY pyRuleName
That's it. Thanks. Didnt think to try the obvious since this was a UAT system and was supposed to have working elastic search
lots of developers fixing things in UAT (no comment) and elastic search indexes were corrupt and they were running old: queries.
Reason i didnt catch it from global db trace is that developers stopped working in system while a large unit test was running
Pegasystems
IN
Cloning the DB is always an issue. Especially having the pr_sys_statusnodes table not truncated before startup of the new nodes. Thanks for the details.