Breaking: mssql-python Adds Native Apache Arrow Support for Zero-Copy Data Transfer

Breaking: mssql-python Adds Native Apache Arrow Support for Zero-Copy Data Transfer

Microsoft's mssql-python driver now fetches SQL Server data directly as Apache Arrow structures, eliminating the need for per-row Python object creation and drastically reducing memory overhead. The feature, contributed by community developer Felix Graßl, promises faster and more efficient data pipelines for users of Polars, Pandas, DuckDB, and other Arrow-native libraries.

“Previously, fetching a million rows meant a million Python objects, a million garbage-collector allocations, and then reconstructing the DataFrame from scratch. Now the data lands in shared memory with zero copies,” said Graßl. “This is a game-changer for large-scale analytics.”

Background: The Arrow Revolution

Apache Arrow defines a standard columnar memory format and a cross-language ABI called the Arrow C Data Interface. This allows different runtimes—C++, Python, Java—to exchange data by simply passing a pointer, with no serialization, no copies, and no re-parsing.

For database drivers like mssql-python, this means the entire fetch loop can run in native code, writing values directly into Arrow buffers. The consuming library (Polars, Pandas, etc.) receives a pointer and starts operations immediately—all without ever materializing a single Python object per row.

Four Concrete Benefits

• Speed: Elimination of per-value Python conversions, especially for temporal types like DATETIME and DATETIMEOFFSET, yields noticeably faster fetches.
• Lower Memory Usage: A column of one million integers becomes a single contiguous C array instead of a million individual Python objects.
• Seamless Interoperability: Data flows directly into Polars, Pandas (via ArrowDtype), DuckDB, Hugging Face datasets, and other Arrow-native tools without intermediate conversion.
• Zero-Copy Pipelines: Subsequent operations—filters, joins, aggregations—all operate in-place on the same Arrow buffers, eliminating any intermediate Python object creation.

What This Means for Data Engineers

“This update effectively removes the Python memory manager as a bottleneck in SQL Server data ingestion,” said Sumit Sarabhai, who reviewed the feature. “For analytics teams already using Polars or DuckDB, this is the missing link for a truly zero-copy ETL pipeline.”

Users can now move from query to analysis in a single step—no more wasteful fetchall() followed by DataFrame construction. The Arrow path is available in the latest mssql-python release and works with any Arrow-compatible library.

For more details on Apache Arrow and the C Data Interface, see the official Arrow documentation.