Supported Applications

---

The ElevateDB .NET Data Provider is a .NET 2.0 data provider. We have tested the data provider successfully with Microsoft Visual Studio 2005 and above.

Calling Dispose

---

Since the ElevateDB .NET Data Provider is indirectly accessing and using unmanaged resources during operation, you should always call the Dispose method for any EDBConnection, EDBCommand, EDBCommandBuilder, or EDBDataAdapter objects when you are done using them (deterministic destruction). Failure to do so can cause major failures in the data provider due to the resources being freed up re-entrantly when the .NET garbage collector thread finalizes these objects.

Database-Agnostic Access

---

The ElevateDB .NET Data Provider includes complete support for database-agnostic access via the factory class architecture in .NET 2.0, and the data provider is automatically registered as a standard data provider in the .NET 2.0 machine.config file during installation. Please see this link for more information on using the ADO.NET 2.0 factory classes:

Writing Generic Data Access Code in ASP.NET 2.0 and ADO.NET 2.0

Visual Studio Query Designer Joins

---

The built-in query designer in Visual Studio defaults to using SQL-89 join syntax (WHERE clause) for INNER JOINs. This is not optimal for ElevateDB because ElevateDB only optimizes joins that are specified via the SQL-92 and higher syntax of JOIN or INNER JOIN. If using INNER JOINs with your queries, please make sure to modify the SQL SELECT statement to use the INNER JOIN syntax instead in order to ensure the fastest possible query execution time. Please see the Optimizer topic for more information on the optimization of joins.