| SQL DB in Microsoft Fabric |
All data is replicated in near-real time to open-source delta parquet format in OneLake. When you deploy a SQL database in Fabric, you get two endpoints: an endpoint to the database and a “SQL analytics endpoint” that allows querying the replicated data in OneLake. This unifies operational and analytics querying while isolating operational analytics workloads. With the SQL analytics endpoint, you can query using the data warehouse engine. Note: This entails that are two endpoints, one for operational use, and second one for analytics. |
SQL Server |
Parquet on Microsoft OneLake |
| TiDB |
Real-time replication of data from OLTP Table to Columnar TiFlash tables. Analytical queries are served by the TiFlash Columnar tables. |
MySQL protocol compatible TiDB |
TiFlash |
| AlloydDB |
Enable the Columnar Engine on the AlloyDB and then either manually add columns to the Columnar Engine or use auto-columnarization, which analyzes your workload and automatically adds columns. |
PostgreSQL |
Google Columnar Engine |
| CedarDB |
Note: No information provided how the Translytical engine works: https://cedardb.com/docs/technology/ |
|
|
| Lakebase |
Neon serverless Postgres DB synced to DeltaLake |
PostgresSQL |
DeltaLake Columnar |