I noticed a poor performance with the new cardinality estimator. In order to fix this you can either:
- switch to compatibilitylevel 120 for your database (MSSQL 2014)
- enable database scoped values to switch to the old estimator (MSSQL 2016)
The stacked view v_policyhistory_lastevaluation is also hammering the performance, I added the MaxDOP option for this (on a server with a lot of processors).
Anybody who has hit the same issues?