SQL
Databases read through DB-API or ADBC with chunked fetch.
How it works
Either an Incremental watermark or a full read. Source types map onto Ingest's canonical type system
on the way in.
The sql plan strategy is read-only, time-boxed and tenant-scoped. It is not a general query surface.
Credential proof
SELECT 1.
Questions
- Which SQL sources has Ingest certified?
- PostgreSQL. Each one has run against the real API, with exact row counts asserted.
- Can Ingest sync any SQL API?
- Ingest authors the connector from the vendor's published API documentation, runs it against the real API, and lists it as deployable only once it passes. A connector is a declarative spec, never per-source code, which is why a new one is authored rather than programmed.
- Where can SQL data land?
- Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake. The data lands in a destination you own, under credentials you control. Ingest keeps no copy of it.
SQL sources, and where they land
Certified SQL connectors: PostgreSQL.
The other source kinds Ingest reads: File, GraphQL, gRPC, REST, SOAP, WebSocket.
Where the tables land: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.