A single static class is used to execute a SQL query - The DbManager class is used to execute a SQL query. The DbManager has methods to create Dataset, DataReader, DataAdapters and Transaction objects. It also allows you to execute a SQL query using ExecuteNonQuery and ExecuteScalar methods. The DbManager class has similar methods as SqlCommand, OracleCommand, etc. It makes the learning curve faster because the developer is already familiar with these methods.
Create a SQL query using the SQL Editor - ADO.NET Accelerator has a SQL Editor to create and test your SQL queries. You don't need to write SQL queries directly in your source code files (cs, vb).
Store every SQL query in a database - You don't have to write strings containing SQL code in your source code files to create a SQL query. One advantage of storing SQL queries in a database is that you can re-use them in multiple applications (e.g. WinForms, ASP.NET) that use the same database. The default mediums to store a SQL query are: XML, Microsoft SQL Server 2000 or superior, and Oracle 10g or superior.
Create database independent data access code - When you execute a SQL query using ADO.NET Accelerator you don't make reference to a particular data provider (e.g. SQL Server, Oracle). Future changes to the database vendor have minimum impact on your existing code.
Support for SQL Server 2000+, Oracle 10g+, ODBC and OleDb - ADO.NET Accelerator supports Microsoft SQL Server 2000 or superior, and Oracle 10g or superior. It also supports multiple databases through generic data providers like ODBC and OleDb.