1.1

If the application is not executing a transaction, then failover occurs transparently to the application. Failed
operations are automatically re-executed if necessary. The application does not receive any exceptions as long
as at least one server is available in the cluster to service network clients.
However, when querying LOB data-types (BLOB/CLOB), clients may receive an SQLFException with State
“XJ217” due to the LOB handle not being found on the new server. In this case, the client may need to retry the
query explicitly (issue #43253 in vFabric SQLFire Limitations on page 687 provides more details).
In this release of SQLFire, if the application is in the middle of a transaction and the server to which client is
connected fails, then the current transaction fails with a connection exception (SQLFException with State
“08006”) and the application must re-execute the transaction. To handle such a case, applications can create a
new connection, and then begin a new transaction and retry the transaction.
Load Balancing
When using the SQLFire locator or a locator embedded inside a server, servers inform the active locator of the
load on each server using the number of current client connections on the server. This allows the locator to
determine the best server to use for a new client connection. In this way, a network client that connects using a
locator is always directed to the least-loaded server in the cluster.
Extensions for Batching and Row Locking
Similar to the JDBC API, the ADO.NET driver provides extensions to the DbCommandAPI to allow for batching
without requiring a DbDataAdapter. Also, the DbDataReader implementation, SQLFDataReader, allows
for expressing the intent to lock rows when executing a SELECT … FOR UPDATE statement. Additional
extensions from the JDBC API are also provided, such as SQLFConnection.AutoCommit.
ADO.NET Driver Classes
All ADO.NET driver implementation classes reside in the VMware.Data.SQLFire namespace.
More InformationDescriptionSQLFire ADO.NET Class
Thrown when a batch operation fails.
Extends SQLFException.
SQLFBatchUpdateException
• VMware.Data.SQLFire.BatchUpdateException on page
665
Creates a connection to SQLFire with
a URL of the form
"Server=<host>:<port>" .
SQLFClientConnection
• Connecting to SQLFire with the ADO.NET Driver on
page 129
• Managing SQLFire Transactions on page 137
Provides several extension methods to
support SQLFire transactions.
• Performing Batch Updates on page 138
• VMWare.Data.SQLFire.SQLFClientConnection on page
665
Implements the .NET
System.Data.Common.DbCommand
class.
SQLFCommand
• Executing SQL Commands on page 130
• Working with Result Sets on page 131
• Specifying Command Parameters with SQLFParameter
on page 134
• VMware.Data.SQLFire.SQLFCommand on page 670
• System.Data.Common.DbCommand (.NET)
SQLFire types. Each type corresponds
to a JDBC type.
SQLFType
• java.sql.Types
• VMware.Data.SQLFire.SQLFType on page 676
Implements the .NET
System.Data.Common.DbDataReader
class.
SQLFDataReader
• Working with Result Sets on page 131
• VMware.Data.SQLFire.SQLFDataReader on page 679
• System.Data.Common.DbDataReader (.NET)
vFabric SQLFire User's Guide128
Developing Applications with SQLFire