• Replies 10 replies
  • Subscribers 336 subscribers
  • Views 153 views
  • Users 0 members are here
Related

SQL Server 2016 (130) compatibility level

David Frederick
$organization

Hi,

Does anyone know whether the impresario database of v14.1 or v15 can safely operate at SQL Server 2016 (130) compatibility level? We are running on SQL Server 2016, but currently using SQL Server 2014 (120) compatibility level. It would be nice to be able to use newer features, such as the STRING_SPLIT() function. 

Thanks,
David

Parents
  • Former Member
    Former Member $organization

    Hi All,

    Just wanted to say that in Development we have seen cases in standard code where the new cardinality estimator causes a noticeable performance hit.  In looking at this we find that if we change the code then we often cause the same issue in the older CE.  Since we have multiple SQL versions running in the field this causes an obvious problem (lots of similar comments show up online).  If you find that you are impacted by increasing the compatibility level, our recommendation for now is to set the new Legacy Cardinality Estimation option that David mentioned and then you should be ok to raise the compatibility level.  A little farther down the road when we make SQL 2016 the minimum supported version we will make the needed code changes so new CE can be used.

    Ron

Reply
  • Former Member
    Former Member $organization

    Hi All,

    Just wanted to say that in Development we have seen cases in standard code where the new cardinality estimator causes a noticeable performance hit.  In looking at this we find that if we change the code then we often cause the same issue in the older CE.  Since we have multiple SQL versions running in the field this causes an obvious problem (lots of similar comments show up online).  If you find that you are impacted by increasing the compatibility level, our recommendation for now is to set the new Legacy Cardinality Estimation option that David mentioned and then you should be ok to raise the compatibility level.  A little farther down the road when we make SQL 2016 the minimum supported version we will make the needed code changes so new CE can be used.

    Ron

Children
No Data