Merk
Tilgang til denne siden krever autorisasjon. Du kan prøve å logge på eller endre kataloger.
Tilgang til denne siden krever autorisasjon. Du kan prøve å endre kataloger.
Note
When you set MultiSubnetFailover=Yes (the recommended setting for Azure SQL Database, Azure SQL Managed Instance, SQL database in Microsoft Fabric, availability group listeners, and failover cluster instances), the driver attempts TCP connections to all resolved IP addresses in parallel, and the TransparentNetworkIPResolution setting doesn't affect the connection sequence. For more information, see High availability and disaster recovery.
TransparentNetworkIPResolution (TNIR) is a legacy multi-IP fallback in the ODBC Driver for SQL Server, available starting with Microsoft ODBC Driver 13.1. It affects the connect sequence when the first resolved IP of the hostname doesn't respond and multiple IPs are associated with the hostname.
TNIR is superseded by MultiSubnetFailover. When MultiSubnetFailover=Yes, the driver attempts TCP connections to all resolved IP addresses in parallel and TNIR doesn't affect the connection sequence. When MultiSubnetFailover=No, TNIR controls the fallback sequence:
| TransparentNetworkIPResolution | Connect sequence |
|---|---|
| Enabled (default) | Try one IP, then all IPs in parallel |
| Disabled | Try all IPs sequentially |
The TransparentNetworkIPResolution connection string and DSN keyword controls this setting at the connection-string level. The default is enabled.
| Keyword | Values | Default |
|---|---|---|
TransparentNetworkIPResolution |
Enabled, Disabled |
Enabled |
The SQL_COPT_SS_TNIR pre-connection attribute allows an application to control this setting programmatically:
| Connection attribute | Size/Type | Values | Default | Description |
|---|---|---|---|---|
SQL_COPT_SS_TNIR (1249) |
SQL_IS_INTEGER or SQL_IS_UINTEGER |
SQL_IS_ON (1), SQL_IS_OFF (0) |
SQL_IS_ON |
Enables or disables TNIR. |