Support for 'multiSubnetFailover' property in JDBC URL for Microsoft SQL Server

Support for 'multiSubnetFailover' property in JDBC URL for Microsoft SQL Server

book

Article ID: KB0073798

calendar_today

Updated On:

Products

TIBCO ActiveMatrix BusinessWorks Plug-in for Database

Description

How to use 'multiSubnetFailover' property in JDBC URL for Microsoft SQL Server.

Issue/Introduction

The "multiSubnetFailover' property for Microsoft SQL Server is supported with TIBCO Database Drivers Supplement Software 2.0.6 Hotfix 001.

Environment

=========== Product: TIBCO ActiveMatrix BusinessWorks Plug-in for Database Version : 7.x,8.x Product: TIBCO Database Drivers Supplement Version: 2.0.6 Hotfix 01 ===========

Resolution

The "multiSubnetFailover' property for Microsoft SQL Server is supported with TIBCO Database Drivers Supplement Software 2.0.6 Hotfix 001.

Please download TIBCO Database Drivers Supplement Software 2.0.6 from the below link.

https://edelivery.tibco.com/storefront/view-component-download.ep?partNumber=01009542

To Download TIBCO Database Drivers Supplement Software 2.0.6 Hotfix 001 please login with credentials at https://support.tibco.com/s/hotfixes and download it from:

Downloads --> Hotfixes --> AvailableDownloads --> _AdditionalProducts --> DBDrivers --> 2.0.6 -->HotFix001

Property: MultiSubnetFailover

Purpose:  Determines whether the driver attempts parallel connections to the failover IP addresses of an Availability Group during initial connection or a multi-subnet failover. When MultiSubnetFailover is enabled, the driver simultaneously attempts to connect to all IP addresses associated with the Availability Group listener when establishing an initial connection or reconnecting after a connection is broken or the listener IP address becomes unavailable. The first IP address to successfully respond to the request is used for the connection. Using parallel-connection attempts offers improved response time over traditional failover, which attempts to connect to alternate servers one at a time.

Valid values:   true | false

Behavior:  If set to true, the driver attempts parallel connections to all failover IP addresses in an Availability Group when establishing an initial connection or reconnecting after a connection is broken or the listener IP address becomes unavailable. The first IP address to successfully respond to the request is used for the connection. This setting is only supported when your environment is configured for Always On Availability Groups.
If set to false, the driver connects to an alternate server or servers as specified by the AlternateServer property when the primary server is unavailable. Use this setting if your environment is not configured for Always On Availability Groups.

Notes:

1.When MultiSubnetFalover is enabled, the virtual network name (VNN) of the availability group listener must be specified with the ServerName connection property.

2.When MultiSubnetFailover is enabled, the driver does not support FailoverMode=select. If MultiSubnetFailover=true and FailoverMode=select, the driver downgrades the FailoverMode to extended and provides the following warning.

failoverMode=select is not supported for AlwaysOn Availability Group,
downgraded to failoverMode=extended

3.When MultiSubnetFailover is enabled, the ConnectionRetryDelay connection property is ignored.

4.If MultiSubnetFailover is enabled and the connection attempt fails, the driver will attempt to connect two more times, regardless of the ConnectionRetryCount setting.

5.When MultiSubnetFailover is enabled, the value of the LoginTimeout property is 15 seconds by default. When LoginTimeout is set to 0 (zero), the driver will still timeout requests after 15 seconds. However, when the value of LoginTimeout is an integer greater than 0 (zero), the driver will timeout requests for the specified duration.

Data source method : setMultiSubnetFailover

Default:    false

Data type:  Boolean

JDBC Driver: tibcosoftwareinc.jdbc.sqlserver.SQLServerDriver

JDBC URL: jdbc:tibcosoftwareinc:sqlserver://<servername>:1433;databaseName=<databaseName>;multiSubnetFailover=<true/false>