Bemærk
Adgang til denne side kræver godkendelse. Du kan prøve at logge på eller ændre mapper.
Adgang til denne side kræver godkendelse. Du kan prøve at ændre mapper.
Applies to:
SQL Server
Azure SQL Database
Azure SQL Managed Instance
Azure Synapse Analytics
Analytics Platform System (PDW)
SQL database in Microsoft Fabric
Note
TransparentNetworkIPResolution is a legacy multi-IP fallback. For Azure SQL Database, Azure SQL Managed Instance, SQL database in Microsoft Fabric, availability group listeners, and failover cluster instances, the recommended setting is MultiSubnetFailover=Yes, which attempts TCP connections to all resolved IP addresses in parallel and uses the first connection that succeeds. When MultiSubnetFailover=Yes, TransparentNetworkIPResolution doesn't affect the connection sequence. For more information, see OLE DB Driver for SQL Server Support for High Availability, Disaster Recovery.
Purpose
TransparentNetworkIPResolution (TNIR) is a legacy multi-IP fallback in the OLE DB Driver for SQL Server. It's superseded by MultiSubnetFailover, which is the recommended setting for Azure SQL Database, Azure SQL Managed Instance, SQL database in Microsoft Fabric, availability group listeners, and failover cluster instances. 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 how the driver handles multi-IP hostnames. The following table uses the Yes and No values accepted by IDBInitialize::Initialize. When you set the property through IDataInitialize::GetDataSource or ADO, use True and False instead.
TransparentNetworkIPResolution |
Behavior when MultiSubnetFailover=No |
|---|---|
Yes (default) |
Try one IP, then all IPs in parallel. |
No |
Try all IPs sequentially. |
Setting Transparent Network IP Resolution
TransparentNetworkIPResolution is enabled by default. MultiSubnetFailover is disabled by default. The following articles provide more information about setting these properties:
- Using Connection String Keywords with OLE DB Driver for SQL Server
- Initialization and Authorization Properties