SQL Server ODBC Driver - Bulk Load Error (unable to find address for bcp_batch)

[BarryJT]

Our SQL Server and Designer licenses have been running smoothly until IT decided to upgrade our machines to Windows 11. We were using the SQL Server Native Client 11.0 ODBC driver to connect to our SQL Server databases. We were using this driver instead of the SQL Server ODBC driver due to issues with the bulk load (error message: Unable to find address for bcp_batch), as discussed in the two links below.  However, now on Windows 11, I'm getting a message that the Native Client is not supported when I try to install it (I know it was deprecated).   

My Designer is currently Version 2023.2.1.276 Patch: 8, but we will be upgrading the Server and Designer soon. The SQL Server ODBC driver is version 10.00.22621.4830. 

Will upgrading the Server and Designer and/or upgrading the SQL Server ODBC driver resolve this issue so we can use bulk load?

Solved: SQL Server Bulk Loader - how to install DSN - Alteryx Community

Solved: SQL Server Bulk Loader unable to find address for ... - Alteryx Community

Thanks,

Barry

[Deano478 · Accepted solution]

@BarryJT One other option could be upgrading you SQL Server ODBC driver to 17.x or 18.x as they are more robust these can be found here: Microsoft ODBC Drivers 

You can configure these either through DSN or Custom Connection Strings and then try testing again as this has allowed me to bulk load in the past.

The driver version you have is most likely the Windows bundled SQL Server ODBC Driver which is quite old.

[BarryJT]

Thank you!  I didn't actually see your response in my inbox (I have to see if I missed it) but I came here to say exactly this!

You are right. I was using the default SQL Server that comes with Windows (you would think Windows 11 would have a more recent version included...). 

I upgraded to the latest version of ODBC Driver 18, and it works. However, it was not straightforward, as I was receiving a server certificate error message that I temporarily solved with TrustServerCertificate=yes in the connection string. I'll be checking with IT to see if this is the correct approach.

Thanks again,

Barry