Universal Data Access Components (UniDAC) is a powerful library of nonvisual cross-database data access components for Delphi, C++Builder, and Lazarus (Free Pascal). The UniDAC library is designed to help programmers develop faster and cleaner cross-database applications. UniDAC is a complete replacement for standard database connectivity solutions and presents an efficient native alternative to the Borland Database Engine and dbExpress for access to Oracle, SQL Server, MySQL, InterBase, Firebird, SQLite, DB2, Microsoft Access, Advantage Database Server, Adaptive Server Enterprise, DBF, NexusDB, and other databases (using ODBC provider), as well as various Cloud services.
UniDAC is based on the well-known Data Access Components from Devart such as ODAC, SDAC, MyDAC, IBDAC, PgDAC and LiteDAC. We have joined the experience of long-term successful development into one great product which provides unified access to popular databases such as Oracle, Microsoft SQL Server, MySQL, InterBase, Firebird, SQLite, DB2, Microsoft Access, Advantage Database Server, Adaptive Server Enterprise, DBF, NexusDB and other databases (using ODBC provider).
The UniDAC library is actively developed and supported by Devart Team. If you have questions about UniDAC, email the developers at email@example.com or visit UniDAC online at https://www.devart.com/unidac/.
UniDAC is very convenient in setup and usage. It provides transparent server-independent interface for working with different databases. Selected database provider ensures the best way to perform operations on the server.
UniDAC provides transparent server-independent interfaces for working with different databases, and lets you change the client engine for specific server type just by changing single connection option. It means that you can easily switch between database servers in your cross-database UniDAC-based application.
UniDAC chooses the best way specific to the server to perform most operations. Every UniDAC data provider uses server-specific native connectivity. All operations with data are performed by providers automatically considering peculiarities of the selected database server.
UniDAC allows developing applications that work with data stored in such Cloud services as: BigCommerce, Dynamics CRM, FreshBooks, Magento, MailChimp, NetSuite, Salesforce, Salesforce MC, SugarCRM, QuickBooks, Zoho CRM. For this, it is enough to use UniDAC ODBC provider with any Devart ODBC drivers for Clouds.
The goal of UniDAC is to enable developers to write efficient and flexible database applications. The UniDAC library is implemented using advanced data access algorithms and optimization techniques. Classes and components undergo comprehensive performance tests and are designed to help you write high-performance, lightweight data access layers.
The UniDAC interface retains compatibility with standard VCL data access components like BDE. Existing BDE-based applications can be easily migrated to UniDAC and enhanced to take advantage of server-specific features.
UniDAC is a cross-database connectivity solution that has been actively developed and supported. UniDAC comes with full documentation, demo projects, and fast (usually within one business day) technical support by the UniDAC development team. Find out more about how to get help or submit feedback and suggestions to the UniDAC development team in the Getting Support topic.
A description of the UniDAC components is provided in the Component List.
The full list of UniDAC features are available in the Features topic.
UniDAC consists of two constituents. The first constituent is the general UniDAC Engine that provides unified programming interface for developers. The second constituent is the data access layer which consists of data access providers. These providers are intended for interacting between UniDAC Engine and database servers. Each data provider works with one specific database server. General UniDAC structure is presented below:
There are two ways to install data access providers. The first way is to install the UniDAC Professional or UniDAC Standard edition. In this case all available providers are installed. The second way is to install UniDAC Engine with the UniDAC Express edition, and required data access providers with Data Access Components such as ODAC, SDAC, MyDAC, IBDAC, and PgDAC. Each DAC installs the corresponding data access provider for UniDAC. However, there is a minor difference between providers installed with UniDAC Professional and providers installed with DACs. Providers installed with UniDAC Professional involve all server-specific functionality, when providers installed with DACs are just wrappers on DAC libraries. If there are both providers for a database server installed, the provider installed with DAC will be used.