This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
We are looking at updating to CU 12 for our SQL Server 2019 installations. Has anyone encountered any major issues with this update? I heard that CU 11 had not fixed the issues with inline scalar functions, is that still the case for CU 12?
Any other information/experience you think might be useful will be appreciated.
Regards,
Michael MacGregor
Database Architect
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(80, 52%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPN%3C/text%3E%3C/svg%3E)
We are seeing some TempDB issues.
We are seeing some TempDB issues.
I have not heard of anything as I can recall.
What issues about scalar functions do you have in mind? I mean that they are not generally broken, but there may specific bugs.
Hi Erland,
According to Brent Ozar, MS is still struggling with the performance of inline scalar functions and CU 11 scalar function inlining is turned off in the following circumstances:
If the query invoking the UDF uses CTEs.
If the UDF references encrypted columns.
If the UDF contains references to WITH XMLNAMESPACES.
Regards,
Mike
As you may know, Microsoft made a very bold change with regards to user-defined scalar functions: they are now being inlined in many cases, and this serves to improve performance in many cases. But since the release of SQL 2019, they have identified a number of situations where inlining results in incorrect results or other undesired behaviour, and the resolution has been in many cases to block inlining in these situations.
I would not really expect very many of them to be unblocked, at least not in SQL 2019, as there probably is major work to do this without undesired side effects.
Of course, if you had a scalar function that was inlined in an earlier build of SQL 2019, and no longer is, you may see a performance regression. Then again, compared to SQL 2017, the performance should be the same.
I know there have also been issues to inlining of scalar functions that have been fixed by other means of unblocking. On the top of my head, I cannot recall any outstanding issue, but what I recall does not say much.
Hi Mike,
I did not find any MS blog or document that announced the issue is fixed in CU12. I check this in MS blog KB5004524 - Cumulative Update 12 for SQL Server 2019.
Quote from the MS blog KB4538581 - FIX: Scalar UDF Inlining issues in SQL Server 2019.
>This cumulative update also blocks inlining in the following scenarios:
>• If the UDF references encrypted columns (added in Microsoft SQL Server 2019 CU11)
>• If the UDF contains references to 'WITH XMLNAMESPACES' (added in Microsoft SQL Server 2019 CU11)
>• If the query invoking the UDF has Common Table Expressions (CTEs) (added in Microsoft SQL Server 2019 CU11)
This blog also did not mention that CU12 fix the issues.
If the response is helpful, please click "Accept Answer" and upvote it, as this could help other community members looking for similar thread.
Hi Cathy,
Thank you.
Though I'm still curious to know if anyone has experienced any other issues with CU 12.
Regards,
Mike