Telerik OpenAccess ORM provides built-in support for a wide range of databases to allow you to connect to one or more databases without the need to install additional components. What is more, the tool allows you to easily switch from using one database to another. It is important for an ORM to support different query languages and Telerik OpenAccess ORM does not impose limits in this regard.
Supported Databases | Commercial Edition | Free Edition |
| Microsoft SQL Azure | Yes | Not Supported |
| Microsoft SQL Server 2000, 2005, 2008, 2012 | Yes | Yes |
| Microsoft SQL Server 2005, 2008 Express | Yes | Yes |
| Microsoft SQL Server Compact 3.5, 4.x | Yes | Yes |
| MySQL 5.x | Yes | Yes |
| Firebird 2.x | Yes | Yes |
| Advantage Database Server 9.1, 10.1 | Yes | Not Supported |
| Sybase SQL Anywhere 11.x, 12.x | Yes | Not Supported |
| Oracle Server 9.2, 10.x, 11.x | Yes | Not Supported |
| Oracle Database 10g, 11g Express Edition | Yes | Yes |
| VistaDB | Yes | Not Supported |
| SQLite | Yes | Yes |
| PostgreSQL 8.4+ | Yes | Yes |
Supported Query Languages
SQL (Structured Query Language) Support
You can use SQL if you need to perform custom operations or just want to re-use your existing SQL statements. To execute a query live on the database, Telerik OpenAccess provides an OQL browser from within your Visual Studio so that you don't need to write any code.
LINQ (Language Integrated Query) Support
OpenAccess ORM offers extensive LINQ support against all supported databases, which has been validated with the Microsoft 101 LINQ to SQL Samples (available in the OpenAccess SDK). The major advantage of LINQ is the compile-time check of your queries – meaning no surprises at run time.
OQL (Object Query Language) Support
OpenAccess supports OQL, another object-oriented query language defined a long time ago by the Object Database Management Group. It was there before the invention of LINQ but now you can use it in such cases where you need to build the query at runtime dynamically.
Using Existing Stored Procedures, Views and Tables
Stored Procedures
OpenAccess allows developers to create new or reuse existing Stored Procedures, and to follow the widely adopted pattern of db logic encapsulation inside the database. Under higher security requirements the stored procedures can be used for all insert, read, update and delete operations to inject additional checks in the database server. A Stored Procedures Editor simplifies the setup and use of stored procedures. If you are working with an Oracle database, you can return even REF cursors from your stored procedures – OpenAccess will automatically generate a method reading the result set and return it to your client code.
Tables and Views
With Telerik OpenAccess ORM you can map database views and tables to classes and vice versa (forward and reverse mapping). The data exposed by the tables and views can be modified and stored back to the database.
Concurrency Mechanisms
OpenAccess supports both optimistic and pessimistic concurrency control. Both approaches can be mixed during runtime. Additionally it is possible to automatically obtain a pessimistic lock upon the first modifying access in an otherwise optimistic transaction. When using optimistic concurrency control (the default), conflicts can be detected by designated version fields, the old content of the modified fields or all fields. And you can also turn conflict detection off.
OpenAccess DataSource Web Server Control
The OpenAccessDataSource control supports data binding scenarios in Web applications that use Telerik OpenAccess ORM. It manages the create, read, update, and delete (CRUD) operations against a data source on behalf of data-bound controls on the same page like grids, bound drop-down list controls, and master-detail pages. The design-time experience is very similar to the other ASP.NET datasource implementations like LinqDataSource or ObjectDataSource controls.
OpenAccess LINQ DataSource Component
This LINQ-enabled data source component targets the RAD developer. It allows you to connect to any supported relational data store such as a database based on the OpenAccess domain model, which can then be consumed by data-bound UI controls, such as RadControls for ASP.NET Ajax. The data source is developed exclusively for .NET 4.0+ enabling support for all the latest enhancements in ASP.NET like query extenders and Dynamic Data support.
Dynamic Data Support
OpenAccess ORM supports the Dynamic Data model (in .NET4) by offering model providers and a Dynamic Data wizard for converting the OpenAccess metadata to the Dynamic Data model.