Skip to main content
Database Administrators

Return to Answer

deleted 92 characters in body
Source Link
Aaron Bertrand
Aaron Bertrand
  • 181.5k
  • 28
  • 402
  • 619

These fixes aren't for the database engine. As I explain here:

Why are there both x64 and x86 packages?

As above, while there is no x86 engine, fixes can apply to a variety of shared components on the machine (including from the feature pack), and I suppose it's possible that those could be installed in isolation on an x86 machine. It is almost certainly the case that if you have installed SQL Server 2016, you should be applying the x64 CU, and only the x64 CU.

These fixes will continue coming out this way because the updates are cumulative - as soon as a fix is there that targets an x86 binary, that fix has to stay in all future CUs too.

These fixes aren't for the database engine. As I explain here:

Why are there both x64 and x86 packages?

As above, while there is no x86 engine, fixes can apply to a variety of shared components on the machine (including from the feature pack), and I suppose it's possible that those could be installed in isolation on an x86 machine. It is almost certainly the case that if you have installed SQL Server 2016, you should be applying the x64 CU, and only the x64 CU.

These fixes will continue coming out this way because the updates are cumulative - as soon as a fix is there that targets an x86 binary, that fix has to stay in all future CUs too.

These fixes aren't for the database engine.

Why are there both x64 and x86 packages?

As above, while there is no x86 engine, fixes can apply to a variety of shared components on the machine (including from the feature pack), and I suppose it's possible that those could be installed in isolation on an x86 machine. It is almost certainly the case that if you have installed SQL Server 2016, you should be applying the x64 CU, and only the x64 CU.

These fixes will continue coming out this way because the updates are cumulative - as soon as a fix is there that targets an x86 binary, that fix has to stay in all future CUs too.

Source Link
Aaron Bertrand
Aaron Bertrand
  • 181.5k
  • 28
  • 402
  • 619

These fixes aren't for the database engine. As I explain here:

Why are there both x64 and x86 packages?

As above, while there is no x86 engine, fixes can apply to a variety of shared components on the machine (including from the feature pack), and I suppose it's possible that those could be installed in isolation on an x86 machine. It is almost certainly the case that if you have installed SQL Server 2016, you should be applying the x64 CU, and only the x64 CU.

These fixes will continue coming out this way because the updates are cumulative - as soon as a fix is there that targets an x86 binary, that fix has to stay in all future CUs too.