Archives of the TeradataForum
Message Posted: Thu, 18 Jun 2015 @ 16:21:58 GMT
I faced some strange situation where Teradata generating wrong execution plans and query running for hours.
Even stats refresh didn't change the plan.
However, dropping all the existing stats and collecting only the stats needed for the query made the query to complete only in few minutes.
Query took only couple of minutes after this. How is this possible and how can we identify which stats were causing the problem? Please suggest.
Please note that in both the cases, explain plan was showing estimated time of few minutes only. However, a product join was not present in the second scenario.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 23 Jun 2019|