Applies ToSQL Server 2016 Developer - duplicate (do not use) SQL Server 2016 Enterprise - duplicate (do not use) SQL Server 2016 Enterprise Core - duplicate (do not use) SQL Server 2016 Standard - duplicate (do not use)

Symptoms

The ALTER SERVER CONFIGURATION with SET SOFTNUMA command does not work correctly in Microsoft SQL Server 2016.

Workaround

To work around this issue, follow these steps:

  1. Stop the SQL Server Agent service.

  2. Run the ALTER SERVER CONFIGURATION with SET SOFTNUMA command.

  3. Restart Microsoft SQL Server.Note The new settings will be applied.

  4. Start SQL Server Agent (optional).

Resolution

The issue was first fixed in the following cumulative update of SQL Server:

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. We recommend that you download and install the latest cumulative updates for SQL Server:

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References

Learn about the terminology that Microsoft uses to describe software updates.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.