CockroachDB vs. NuoDB vs. Oracle MySQL HeatWave vs. SQL Server Data Access Components Comparison Chart

The world is moving to distributed applications and architectures, and your database should too. Learn how you can deploy where you want, when you want, and how you want with a distributed SQL database. Migrate existing SQL applications to a distributed, multi-node architecture that can dynamically scale out and in. Our Transaction Engines (TEs) and Storage Managers (SMs) work together to ensure ACID compliance across multiple nodes. Deploy in a distributed architecture. When you deploy your database with multiple nodes, the loss of one or multiple nodes will not result in the loss of database access. Deploy TEs and SMs to meet your variable workload needs, or deploy in the different environments the teams in your organization uses: in private and public clouds, in hybrid environments, and across clouds.

Enjoy the highest performance and unlimited possibilities when working with SQL Server. SQL Server Data Access Components (SDAC) is a library of components that provides native connectivity to SQL Server from Delphi and C++Builder including Community Edition, as well as Lazarus (and Free Pascal) for Windows, Linux, macOS, iOS, and Android for both 32-bit and 64-bit platforms. SDAC-based applications connect to SQL Server directly through OLE DB, which is a native SQL Server interface. SDAC is designed to help programmers develop faster and cleaner SQL Server database applications. SDAC, a high-performance, and feature-rich SQL Server connectivity solution is a complete replacement for standard SQL Server connectivity solutions and presents an efficient native alternative to the Borland Database Engine (BDE) and standard dbExpress driver for access to SQL Server. SDAC-based DB applications are easy to deploy, and do not require the installation of other data provider layers.