Skip to main content

Drivers

Three published drivers, one shared shape. Each speaks its database's wire protocol directly and returns Apache Arrow end to end. Pick yours below; every driver has the same set of pages — connection, authentication, data types, compatibility, examples, troubleshooting, licensing, environment variables, and what's new.

Microsoft SQL ServerArrowTDSNative MS-TDS 7.4. Azure SQL & Microsoft Fabric, SQL / integrated / Entra ID auth, geospatial & VECTOR types.v0.5.25 Azure SQL · FabricPostgreSQLArrowFEBENative Frontend/Backend v3, no libpq. NUMERIC → decimal with no string detour, SCRAM / Kerberos / GSS auth.v0.3.8 PG-compatibleOracleArrowTTCNative TNS + TTC, no OCI or Instant Client. Oracle Cloud Autonomous Database, OCI IAM & Entra ID tokens, Kerberos.v0.2.8 Oracle Cloud ADB

What's the same across the family​

  • Load by name. Every driver installs an ADBC manifest, so clients connect with driver="arrowtds" / "arrowfebe" / "arrowttc" — no library path.
  • Three ways to connect. Discrete adbc.arrow<code>.* options, an ADO.NET connection string, or a URI. Structured options always win.
  • Shared diagnostics & licence via the ARPEIO_ADBC_* environment variables.
  • Arrow end to end — results decode straight into Arrow column buffers, no intermediate row objects.

What differs​

Each database brings its own types, auth methods and cloud services — that's what the per-driver pages cover. See each driver's Compatibility page for the exact support matrix and any not-yet-implemented surface.