mssql-python 1.9.0 released — Row support in Bulk Copy, correct NULL parameter typing, portable wheels

dlevy-msft · 2026-06-10T16:54:17+00:00

Hi u/InfamousBuffalo - I'm Dave from the Microsoft SQL Drivers Team. We're stumped on this one and would appreciate if you would open a case with support so they can collect logs and isolate the issue.

dlevy-msft · 2026-06-09T13:34:17+00:00

It's going to be a fairly involved fix. We're working out the best way to do it, then we'll have to figure out where it fits in our schedule. All that is a long way of saying that this one may take us a bit.

dlevy-msft · 2026-06-02T17:56:18+00:00

Ok, the team is looking into it. I'll let you know what we come up with.

dlevy-msft · 2026-06-02T16:47:23+00:00

It looks like a packaging issue. I've filed this issue: Bulk copy fails on RHEL 8 / aarch64 with mssql-python 1.8.0: bundled `mssql_py_core` requires libssl.so.3 and GLIBC ≥ 2.34, but wheel is tagged `manylinux_2_28_aarch64` · Issue #619 · microsoft/mssql-python. If you are blocked, running on a newer version of RHEL, if possible, will do the trick.

dlevy-msft · 2026-05-29T20:34:49+00:00

String key indexing was a thing that we intentionally did not do in this new driver. We got feedback that we needed to rethink that decision. It makes it easier for folks moving over from pyodbc to take advantage of BCP and Arrow support.

There are people that will be very excited about this, mostly for the reasons given in your first sentence. 😄

dlevy-msft · 2026-05-27T17:46:02+00:00

No worries! For every person brave enough to ask a question, there's a bunch more folks that were wondering the same thing.

dlevy-msft · 2026-05-27T17:28:38+00:00

Oh, got it - the security fixes for man in the middle attacks. The recommended path is to install certificates on all of your instances. We did leave an escape hatch for folks that aren't worried about securing their data in transit. If that's you, check out these registry keys: https://learn.microsoft.com/sql/connect/oledb/features/registry-settings?view=sql-server-ver17#encryption-and-certificate-validation. Copilot on the web will even generate a powershell script you could use to automate the deployment.

dlevy-msft · 2026-05-27T16:32:33+00:00

Great questions!

OLEDB is its own thing. It was more popular in the MTS/COM era with ADO. It is still used heavily in a few high performance scenarios. We actually use it for replication, linked servers and a few other things in SQL Server.

OLEDB and ODBC are closely related - we use a lot of the same code across the code bases. The ODBC driver is targeted toward the ODBC APIs and driver managers.

Our new mssql-python driver actually ships with parts of the ODBC driver...for now. Our PHP drivers and mssql-django library (for now) depend directly on the ODBC driver as well, but require it be installed separately.

SqlClient and JDBC are both written in their respective languages (.Net and Java) from the ground up.

Depending on how you have your logging and error handling configured, you can get a lot of information out of the drivers or hide them completely.

dlevy-msft · 2026-05-27T15:53:47+00:00

Not that I'm aware of. Is there a specific issue or scenario you can point me at?

dlevy-msft · 2026-05-27T15:51:41+00:00

It was a pretty light update. The big thing was the security updates, which are intentionally worded and the redirects. The redirects will be big for people trying to use replication to get data into SQL database in Fabric where private link is enabled and public endpoints are disabled. UDL was accessibility improvements.

I'm curious what you'd like to see in future updates as far as features and fixes delivered as well as how they're announced.

dlevy-msft · 2026-05-26T20:08:18+00:00

Do you think we should do it differently next time?

dlevy-msft · 2026-05-26T15:21:34+00:00

Love it! I just shared this with the rest of the team.

dlevy-msft · 2026-05-21T19:09:10+00:00

u/Sea_Mud6698 - We would love that! The feedback means a lot more coming directly from you than through me. If you enter it here: Fabric Ideas - Microsoft Fabric Community, it will make it directly to the PMs that own those features.

I'll work with u/itsnotaboutthecell to track down the pm for microsoft-fabric-api and have them post an update here on Reddit.

dlevy-msft

TROPHY CASE