This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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(134.4, 13%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EUD%3C/text%3E%3C/svg%3E)
New year wishes to all.
I wanted to know about any potential impact to SQL server services on applying Microsoft .NET Framework Security Updates on SQL server host. Below are the details of my OS and SQL server version.
![](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(236.8, 68%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDB%3C/text%3E%3C/svg%3E)
If there were any known issues with a Windows update and a supported version of SQL Server, there would be a Knowledge Base article about it, and a fix in the works.
Hi David,
Yes I did go through the notes, but it is not clear to me whether this .net framework has fixed that issue or will introduce that issue.
https://devblogs.microsoft.com/dotnet/net-framework-august-2020-security-and-quality-rollup-updates/
SQL
– SqlBulkCopy.WriteToServer can cause transactions to in-memory SQL tables, to fail. The client may see an exception with message “Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.” SqlBulkCopy.WriteToServer was sending an Attention token (cancellation message) after sending data to Sql Server, causing the server to abort the transaction for in-memory tables.
Nothing specific to SQL server in Jan 2020 . Does that mean we are good to go?
https://support.microsoft.com/en-in/help/4532933/kb4532933-cumulative-update-for-net-framework
The issue discussed about SqlBulkCopy is a client-side thing. When it comes to SQL Server itself, it could be affected if there is a change which is used in the SQLCLR, including any assemblies you may have yourself. And, yes, you could have an assembly that uses SqlBulkCopy, but it is not the most likely.
And what David is saying is that if there are any known issues, Microsoft would take care of them quite directly.