Recent upgrade of SQL causes some reports to no longer work due to New estimator
![]() Upgrade from SQL 2012 TO SQL 2019
Have 4 very complex reports that are failing:
Error: The query processor ran out of internal resources and could not create query plan.
I would like to put into my advanced SQL the following to force the use of the 2012 CE but it does not seems to be reading correctly in JRS.
OPTION (USE HINT (‘FORCE_LEGACY_CARDINALITY_ESTIMATION’)
this will give us time to rebuild the report and move forward.
Has anyone been able to use this type of SQL command in JRS?
|
Be the first one to answer this question!
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
Which ELM Tool version?