I have 2 SQL Server CU patch questions, for SQL 2014, 2016SP2, 2017, 2019.
Is it required to reboot server AFTER applying SQL CU?
We are trying to use SCCM to deploy SQL CU and MS patches to our servers.
We have SQL 2016SP2, 2017, 2019 running on a mixed Windows OS version, some are Win2016, some are Win2019.
I want to have SCCM to push SQL 2017 CU to a bunch of servers that contains SQL 2016SP2, SQL2017, SQL 2019 standalone instances.
My manual testing tells me, that a SQL 2017 CU will be rejected by SQL 2019 Instance during patch validation step. But somehow, the CU extraction and setup process installed Microsoft Visual C++ 2010 on my SQL 2019 instance server.
Do you think it presents any harm?
Does anyone have SCCM SQL CU patch automation experience?