Skip to main content

What's new in ArpeMSSQL

Feature-oriented release highlights for ArpeMSSQL — the pure-native SQL Server ADBC driver that streams Apache Arrow end-to-end.

Get it in one line — see the install guide:

curl -fsSL https://raw.githubusercontent.com/arpe-io/adbc-drivers/main/install.sh \
  | sh -s -- arpemssql --license ./arpeio_adbc.lic

Verified TLS options — October 2026 (v0.7.0)​

New options adbc.arpemssql.tls_ca_file and HostNameInCertificate; query_timeout applies.

Read-only routing — October 2026 (v0.6.7)​

ApplicationIntent=ReadOnly; SQL type name in field metadata (ARPEMSSQL:type).

SqlBulkCopy option parity — October 2026 (v0.6.6)​

New option arpemssql.bulk_order; arpemssql.bulk_keep_identity fixed.

Ingest safety — September 2026 (v0.6.5)​

All-or-nothing bulk ingest; new option arpemssql.bulk_atomic.

Nanosecond ingest fix — September 2026 (v0.6.4)​

Arrow nanosecond timestamps and times ingest at the right value.

Parameter streams without ingest — September 2026 (v0.6.3)​

AdbcStatementBindStream works without a bulk-ingest target.

Microsecond timestamps by default — September 2026 (v0.6.2)​

New option adbc.arpemssql.timestamp_precision.

ArrowTDS becomes ArpeMSSQL — September 2026 (v0.6.1)​

Rebrand: driver, options and URI scheme renamed.

RHEL 8 support & leaner defaults — September 2026 (v0.6.0)​

The shipped Linux driver now runs on RHEL 8 / Rocky 8 and every newer distro out of the box (self-contained, static OpenSSL). The default read batch size also drops from 100,000 to 32,000 rows for a lighter memory footprint — output stays byte-for-byte unchanged.

Write geospatial data, not just read it — August 2026 (v0.5.25)​

ArpeMSSQL already read geometry/geography columns as GeoArrow WKB — now it writes them too. On adbc_ingest, Arrow WKB cells convert client-side to SQL Server's native spatial format and bulk-load, with full geometry coverage (points through nested collections, Z/M/ZM, empties) and automatic SRID handling. See Data types.

Hardened release binaries — August 2026 (v0.5.24)​

Security hardening of the shipped binaries. No driver behaviour change.

Sturdier sessions and stronger secret hygiene — August 2026 (v0.5.23)​

A security and robustness pass on the wire-parsing, authentication, and ingest paths: secrets (Entra tokens, URI passwords) are scrubbed from memory before free, a multi-statement query no longer returns a half-read session to the pool, and malformed wire metadata is rejected rather than mis-parsed.

SQL Server 2025 VECTOR type — August 2026 (v0.5.22)​

Round-trip support for the SQL Server 2025 VECTOR(n) type — read as Arrow fixed_size_list<float32>[n] and ingested straight back into a VECTOR(n) target, with no server-side cast. See Data types.

Microsoft Entra ID authentication — August 2026​

Connect to Azure SQL Database and Microsoft Fabric with Microsoft Entra ID (Azure AD) — no passwords. Four options: bring your own token, service principal, managed identity, or the default credential chain that runs unchanged from laptop to CI to production. See Connection → Entra ID.

Azure SQL "Redirect" policy — August 2026​

ArpeMSSQL now follows Azure SQL and Fabric's Redirect connection policy transparently, reconnecting to the routed database node — previously only Proxy worked. (Redirect needs outbound TCP on ports 11000–11999.)

A standalone driver you install by name — August 2026 (v0.5.19)​

ArpeMSSQL is now an independently installable ADBC driver: one-line install of a checksum-verified binary, load by name (driver="arpemssql"), and portable sqlserver:// / mssql:// / arpemssql:// connection URIs.

Faster, more reliable connections — July 2026 (v0.5.18)​

A reworked connect path: when a host resolves to several addresses they share one timeout budget, so a single dead address (a stray link-local entry on Windows, say) can no longer stall the connection.

Faster large extracts — July 2026 (v0.5.15)​

A decode-path rework removed a scaling bottleneck under high parallelism — part of an overall ~4.6× speed-up on the reference SQL Server extract benchmark.

Native geospatial, decimal, and LOB types — 2026​

geometry / geography columns come back as interoperable GeoArrow / WKB (Z/M and curved geometries preserved), and text/ntext/image LOBs, money/smallmoney, uniqueidentifier, and xml all decode natively. See Data types.

Integrated authentication on Windows — May 2026 (v0.4.5)​

Trusted/integrated auth with no username or password on Windows, via SSPI (Kerberos). See Authentication.

The native TDS engine — foundational​

From the start, ArpeMSSQL speaks MS-TDS directly over TCP/TLS — no ODBC, no FreeTDS. Native bulk ingest into INSERT BULK, streaming Arrow fetch as the server produces rows, and the full ADBC 1.1.0 surface.

To report an issue or request a licence, contact sales@arpe.io or visit https://www.arpe.io.