mssql-python Now Integrates Apache Arrow for Blazing-Fast SQL Server Data Transfer

Breaking: mssql-python Adds Apache Arrow Support

mssql-python, the official Python driver for SQL Server, now supports fetching data directly as Apache Arrow structures. This update eliminates the traditional overhead of converting SQL Server result sets into Python objects, offering a zero-copy path to Polars, Pandas, DuckDB, and other Arrow-native libraries.

Community developer Felix Graßl contributed the feature, which dramatically speeds up data transfer for users working with large datasets. “The previous method required building a million Python objects to load a million rows—now those rows flow directly into Arrow buffers with no per-row Python overhead,” Graßl said.

Lead reviewer Sumit Sarabhai confirmed the improvement: “This is a game-changer for high-throughput pipelines. Data scientists will see noticeable gains, especially when using temporal types like DATETIME or DATETIMEOFFSET.”

Background: What Is Apache Arrow?

Apache Arrow defines a columnar in-memory format and a cross-language ABI (Arrow C Data Interface). Instead of storing a table as a list of rows (each row a collection of Python objects), Arrow stores all values for a column contiguously in a typed buffer. Nulls are tracked with a compact bitmap rather than per-cell None objects.

The key is zero-copy language interoperability. Any library that implements the Arrow C Data Interface can exchange data via a simple pointer—no serialization, no copying, no re-parsing. A C++ database driver and a Python DataFrame library can work on the exact same memory without knowing about each other’s internals.

For mssql-python, this means the entire fetch loop can run in C++ and write values directly into Arrow buffers. No Python object creation per row, no garbage-collector pressure. The receiving library (Polars, Pandas, DuckDB) gets a pointer and starts operating immediately. Subsequent operations like filters, joins, and aggregations also work in-place on those same buffers.

What This Means for Developers

The integration delivers four concrete benefits:

• Speed: Columnar fetch avoids Python object creation per row, making fetching faster for many SQL Server types. Temporal types like DATETIME and DATETIMEOFFSET see the biggest gains because Python‑side per‑value conversions are eliminated.
• Lower memory usage: A column of one million integers becomes a single contiguous C array, not a million individual Python objects. This drastically reduces memory footprint.
• Seamless interoperability: Data flows directly into Polars, Pandas (via ArrowDtype), DuckDB, Hugging Face datasets, and other Arrow-native tools without intermediate formats.
• Simplified code: Developers can now write efficient data pipelines without manual optimization for row‑by‑row conversions. The driver handles zero‑copy under the hood.

“With this feature, mssql-python bridges the gap between SQL Server and the modern Python data ecosystem,” said Graßl. “Users can now build end‑to‑end analytics workflows that never materialize intermediate Python objects.”

The update is available immediately in the latest release of mssql-python. Existing users can upgrade to take advantage of the Arrow path with minimal code changes—just enable the Arrow mode when opening a connection.

Key Terms

• API: A source‑code contract that defines how to call a function or library.
• ABI: A binary‑level contract that specifies how compiled code is laid out in memory. Two programs built in different languages can share an ABI and exchange data directly—no serialization needed.
• Arrow C Data Interface: Apache Arrow’s ABI specification—the standard that makes zero‑copy data exchange between languages possible.

For more details, see the official mssql-python repository.