microsoft sql server jdbc driver location

The primary server in that case actually supplies the connection string to the failover partner and we ignore what you put in the actual application connection string. If we were able to successfully connect to the Primary Server once, we will cache the failover connection string via the connection to the Primary server. In this case, we are either connecting to a named instance (by way of the port), or a default instance on a non-standard port (that being 1433). Jdbc:sqlserver://myserver1 databaseName=AdventureWorks failoverPartner=myserver2:1699 Again this should work perfectly fine from a usage standpoint of failoverPartner. In this situation, we are connecting to a named instance for the failoverPartner. Jdbc:sqlserver://myserver1 databaseName=AdventureWorks failoverPartner=myserver2instance This connection string should work perfectly fine. If the primary server becomes unresponsive, we will fail over to the myserver2. In this connection string, our Primary server will be myserver1 with our failover server being myserver2. Jdbc:sqlserver://myserver1 databaseName=AdventureWorks failoverPartner=myserver2 We ran into some interesting situations with the SQL 2005 JDBC Driver (v1.2) and it's use with failover partners.

Microsoft sql server jdbc driver location