Skip to main content

FastTransfer 1.0: Built-in ADBC Drivers, Db2 and the Physical Method

The ARPEIO Team
The ARPEIO Team
2026-11-19 · 9 min · Release · FastTransfer
TL;DR

FastTransfer 1.0 is the first major release. It bundles six Arpe.io ADBC drivers (SQL Server, PostgreSQL, Oracle, Db2, Teradata and Netezza) that move rows as Arrow columns from source to target, with nothing to install. On a 6-million-row table, cross-database transfers run 1.5 to 2.1 times faster than with the vendor drivers, and Oracle to Oracle 14 times faster. Db2 for LUW becomes a source and a target, one Physical method replaces the four engine-specific ones, and the SQL Server physical split is up to 3.7 times faster.

FastTransfer 1.0 moves Apache Arrow columns between six ADBC drivers: adbc_mssql, adbc_pgsql, adbc_oracle, adbc_db2, adbc_teradata and adbc_netezza, each usable as a source and as a target

FastTransfer 1.0 adds a new data path. With an adbc_* connection type on both ends, rows are read and written as Arrow columns by the Arpe.io ADBC drivers that ship inside the binary.

The release also adds Db2 for LUW, makes choosing a parallel method simpler, and tightens a few things around reliability and security. If you run 0.18 today, read the upgrade notes before you deploy.

6
ADBC drivers, bundled
nothing to install
2.1x
Oracle to PostgreSQL
6 M rows, 6.8 s to 3.2 s
14x
Oracle to Oracle
6 M rows, 47.7 s to 3.4 s
3.7x
SQL Server physical split
clustered table, 8 streams

New ADBC connections​

1.0 adds six connection types. Each one works as a source and as a target.

SQL ServerSQL Server
  • adbc_mssql
PostgreSQLPostgreSQL
  • adbc_pgsql
OracleOracle
  • adbc_oracle
IBM Db2Db2 for LUW
  • adbc_db2
TeradataTeradata
  • adbc_teradata
IBM NetezzaIBM NetezzaNetezza
  • adbc_netezza

The drivers are part of FastTransfer: there is no client to install and nothing to configure. The source driver hands Arrow columns to the target driver, and no row is converted on the way.

The command line does not change. The same server, database, user, password and trusted authentication parameters apply, and so do all parallel methods. Only the connection type is new:

.\FastTransfer.exe `
--sourceconnectiontype "adbc_oracle" `
--sourceserver "oraserver:1521/ORCLPDB1" `
--sourceuser "TPCH" `
--sourcepassword "mypassword" `
--sourceschema "TPCH" `
--sourcetable "ORDERS" `
--targetconnectiontype "adbc_mssql" `
--targetserver "localhost" `
--targettrusted `
--targetdatabase "tpch" `
--targetschema "dbo" `
--targettable "orders" `
--parallelmethod "Physical" `
--degree 8 `
--loadmode "Truncate"
Before you switch
  • Both ends must use an adbc_* type.
  • The drivers run on Windows x64 and Linux x64.
  • They need an ADBC driver block in your license file. Contact Arpe.io to have it added.

Performance FastTransfer 0.18 vs 1.0​

The test table is LINEITEM from TPC-H SF1, 6 million rows, transferred with the RangeId method and a degree of 4. Each figure is the median time in seconds, with the vendor driver and with the Arpe.io ADBC drivers.

LINEITEM, 6 M rows, RangeId, degree 4, FastTransfer 0.18 vs 1.0 (median, seconds)
Source → TargetVendor driverArpe.io ADBC driversGain
SQL Server → PostgreSQL6.7 s3.7 s1.8x
PostgreSQL → SQL Server5.1 s3.3 s1.5x
Oracle → SQL Server6.8 s3.6 s1.9x
Oracle → PostgreSQL6.8 s3.2 s2.1x
SQL Server → SQL Server5.9 s4.4 s1.3x
Oracle → Oracle (degree 1)47.7 s3.4 s14x
LINEITEM, 6 M rows, cross-database transfers, FastTransfer 0.18 vs 1.0 (median, seconds)
Lower is better
  • Vendor driver
  • Arpe.io ADBC drivers
SQL Server → PostgreSQL, vendor6.7 s
SQL Server → PostgreSQL, ADBC3.7 s
PostgreSQL → SQL Server, vendor5.1 s
PostgreSQL → SQL Server, ADBC3.3 s
Oracle → SQL Server, vendor6.8 s
Oracle → SQL Server, ADBC3.6 s
Oracle → PostgreSQL, vendor6.8 s
Oracle → PostgreSQL, ADBC3.2 s
  • Across databases, the ADBC path cuts the time by a third to more than half: 1.5 to 2.1 times faster.
  • Between two SQL Server instances, the gain is smaller, 1.3 times.
  • Oracle as a target is where the change shows most: 47.7 seconds down to 3.4, 14 times faster, with a degree of 1.

Db2 for LUW, source and target​

Db2 for LUW joins the supported databases, as a source and as a target, through adbc_db2. It also gets the parallel methods that fit it:

  • DBPartition reads the data partitions of a Db2 table.
  • Random now uses the right modulo syntax on Db2, and on Teradata too.

DBPartition also works with the ADBC types of SQL Server, PostgreSQL, Oracle and Teradata.

One method for physical splits: Physical​

Every engine has its own way to locate a row on disk, and until 0.18 you picked the FastTransfer method that matched it: Ctid, Rowid, Physloc or NZDataSlice. With --parallelmethod Physical, FastTransfer picks it from the source:

There is no key column to choose. Give the source schema and table, and a degree.

A faster physical split on SQL Server​

The physical split of a SQL Server table now spreads the rows evenly over all streams, on rowstore tables and on clustered columnstore tables. On a clustered rowstore table with 8 streams, the transfer went from about 17.7 seconds to 4.7.

Physical split of a clustered SQL Server table, 8 streams (seconds)
Lower is better
  • FastTransfer 0.18
  • FastTransfer 1.0
FastTransfer 0.1817.7 s
FastTransfer 1.04.7 s

Reliability and security​

Hidden passwords

Passwords in uri= connection strings are hidden in all logs.

Signed build provenance

Each release download comes with SLSA build provenance, so you can check that a binary was built from the FastTransfer sources.

Upgrading from 0.18​

Deprecated parallel methods

Ctid, Rowid, Physloc and NZDataSlice still work in 1.0, with a warning. They will be removed in 2.0. Switch to Physical now.

A few commands that ran on 0.18 need a change:

CaseIn 1.0
Physloc, or Physical on SQL ServerNeeds --sourceschema and --sourcetable. A --query can still filter the table.
NZDataSlice, or Physical on NetezzaNo longer needs --sourceschema and --sourcetable.
Oracle source, PARTITION (...) in the FROM of --queryRefused. Use the DBPartition method instead.

Known limitations​

No ADBC on Linux ARM64

The ADBC connection types run on Windows x64 and Linux x64 only.

Time zone offsets

With ADBC, values with a time zone offset from SQL Server and Oracle arrive as the same instant in UTC.

Db2 and Teradata targets

A few data types are not supported yet as ADBC targets, such as Db2 DECFLOAT and Teradata PERIOD.

In the Command Wizard​

The Command Wizard offers the ADBC connection types and the Physical method, so you can build a 1.0 command without looking up the parameter names.

Try FastTransfer

Free 30-day trial

Resources​