PPS Advisory: Microsoft SQL Server 2014 Cost Estimator Bug With Siebel Results In Very Bad Execution
Hi All,
Wanted to pass this along since it created a huge mess on a current IP 2016 upgrade for me. In SQL
Server 2014 the Cost Estimator (CE) has been rewritten. We have been seeing horrible executing plans
related to the CE not avoiding sorts where it should.
For example for account position with the position id 0-5220 the optimizer should know there will be a ton of records and therefore should
use the OOTB index to find the records for sadmin’s position and to also avoid the sort. We checked our database
statistics and can see 0-5220 is in the histogram so the CE knows exactly how