Failover Support in DataDirect ADO.NET Data Providers

In today's business environment, you need to ensure that the data on which your critical .NET applications depend is always available. This document describes why it is important that your ADO.NET data provider includes connection failover support.

The DataDirect Connect for ADO.NET 3.0 data providers support the following useful features that help your data remain available:

Connection failover, which allows an application to connect to an alternate database server if the primary database server is unavailable.

Connection retry, which defines the number of times that the data provider attempts to connect to the primary and alternate database servers after the first unsuccessful connection attempt.

Client load balancing, which changes the order in which the servers are accessed. You can use client load balancing with connection failover to help distribute new connections in your environment so that no one server is overwhelmed with connection requests.

Summary and More Information about DataDirect ADO.NET Data Providers

Of course, for connection failover, client load balancing, and connection retry to work, an underlying replication mechanism must be used to ensure data consistency.

NOTE: Code examples in this document use the generic DbProviderFactories syntax introduced in the Microsoft .NET Framework 2.0. If you are using the .NET Framework 1.x or DataDirect Connect for .NET 2.2 data providers, refer to Failover Support: DataDirect Connect for .NET Data Providers.