April 16, 2018 at 2:24 pm
As referenced from the link below, if I installed KB4057118, released on 01/04/18, does it include any of the CU updates from a previous date? I have a client that updated their SQL 2016 box over the weekend with "everything that was released prior to 03/14/18". If their statement were true, wouldn't they be at version build 13.0.4466.4, not version build number 13.0.4210.6, which is what it currently is showing?
https://buildnumbers.wordpress.com/sqlserver/#SQL2016
Thanks.
April 16, 2018 at 4:40 pm
The latest patch for MS SQL Server can be found on the official Microsoft web site - https://technet.microsoft.com/en-us/library/ff803383.aspx KB4057119 is CU7 for SP1 https://support.microsoft.com/en-us/help/4057119/cumulative-update-7-for-sql-server-2016-sp1 which is the build 13.0.4466.4.
April 16, 2018 at 4:51 pm
They won't update to that in production yet b/c it is "too recent". I just need to make sure they are at least updated to CU2 for SQL 2016 SP1, which is 13.0.4422.0. The confusion is, why does update 13.0.4210.6 have a lower build number than CU2 but has a release date that much newer (Jan 4 2018)?
April 18, 2018 at 9:34 am
We talked them into updating to the latest CU, so there is no more concern. However, I'm still curious. I'm assuming the security updates and CUs are mutually exclusive from each other; both need to be installed? A security update does, even though it has a more recent release date than that of a CU, the CU still needs to be installed?
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply