Skip to content

Latest commit

 

History

History
59 lines (46 loc) · 3.32 KB

File metadata and controls

59 lines (46 loc) · 3.32 KB
title Map TCP IP Ports to NUMA Nodes (SQL Server) | Microsoft Docs
ms.custom
ms.date 03/14/2017
ms.prod sql
ms.prod_service high-availability
ms.reviewer
ms.suite sql
ms.technology configuration
ms.tgt_pltfrm
ms.topic conceptual
helpviewer_keywords
NUMA
memory [SQL Server], NUMA
affinity NUMA
ports [SQL Server], working with NUMA
CPU [SQL Server], NUMA support
NUMA, How to map a port to a NUMA node
NUMA affinity
TCP/IP [SQL Server], NUMA support
non-uniform memory access
ms.assetid 07727642-0266-4cbc-8c55-3c367e4458ca
caps.latest.revision 20
author MikeRayMSFT
ms.author mikeray
manager craigg

Map TCP IP Ports to NUMA Nodes (SQL Server)

[!INCLUDEappliesto-ss-xxxx-xxxx-xxx-md] This topic describes how to map TCP/IP ports to non-uniform memory access (NUMA) nodes by using [!INCLUDEssNoVersion] Configuration Manager. On startup, the [!INCLUDEssDE] writes the node information to the error log.

To determine the node number of the node you want to use, either read the node information from the error log, or from the sys.dm_os_schedulers view. To set a TCP/IP address and port to single or multiple nodes, append a node identification bitmap (an affinity mask) in brackets after the port number. Nodes can be specified in either decimal or hexadecimal format. To create the bitmap, first number the nodes from right to left starting with zero, as in 76543210. Create a binary representation of the node list, providing 1 for nodes you want to use, and 0 for nodes you do not want to use. For example, to use NUMA nodes 0, 2, and 5, specify 00100101.

NUMA node number 76543210
Mask for 0, 2, and 5 counting from right 00100101

Convert the binary representation (00100101), into decimal [37], or hexadecimal [0x25]. To listen on all nodes, provide no node identifier.

If a port is mapped to more than one NUMA node, [!INCLUDEssNoVersion] assigns connections to nodes in a round-robin fashion without attempting to balance load across the nodes.

Note

To enable [!INCLUDEssNoVersion] to listen on multiple TCP ports for each IP address, see Configure the Database Engine to Listen on Multiple TCP Ports.

Using SQL Server Configuration Manager

To map a TCP/IP port to a NUMA node

  1. In [!INCLUDEssNoVersion] Configuration Manager, expand SQL Server Network Configuration, and then click Protocols for <instance name>.

  2. In the details pane, double-click TCP/IP.

  3. On the IP Addresses tab, in the section corresponding to the IP address to configure, in the TCP Port box, add the NUMA node identifier in brackets after the port number. For example, for TCP port 1500 and nodes 0, 2, and 5, use 1500[37], or 1500[0x25].

See Also

Soft-NUMA (SQL Server)