go-sqlcmd icon indicating copy to clipboard operation
go-sqlcmd copied to clipboard

BCP supports with ODBC Driver 18

Open mikependon opened this issue 1 year ago • 2 comments

We are using the BCP utility to bulk insert huge number of rows towards our Data Lake Data Warehouse (a dedicated SQL Pool in Azure) and it is kind of a very important capability to us.

The current released version of BCP is only supporting the ODBC Driver v17.

image

Our organization has already started the rollout of the ODBC Driver v18 to complement the requirement of Security Vulnerabilities.

Though we can still utilize the BCP in our Azure Kubernetes Services by just referencing the older version of mssqltools17 as defined here, but still it fails to run from various Windows-based platform now where has the updated ODBC drivers.

Is there a plan to support the latest ODBC driver v18? And if yes, when do we expect it? Thanks

mikependon avatar Apr 17 '24 11:04 mikependon

Hey @shueybubbles is there any chance you could look into this? ODBC v17 has CVEs our company is wanting to address by updating to v18. Thanks!

matthewhilldev avatar Aug 07 '24 06:08 matthewhilldev

Hey @matthewhilldev - It's a bit outside the scope of this work here, but there were breaking changes between ODBC 17 and 18 around connection security. To allow customers to phase in this change, BCP 18 has a different path than BCP 17 so they can run side by side. The BCP you use must be the same version as the drivers installed so BCP 17 uses ODBC 17 and BCP 18 uses ODBC 18. Here is a link for the various downloads: https://learn.microsoft.com/en-us/sql/tools/bcp-utility?view=sql-server-ver16&tabs=windows#download-the-latest-version-of-the-bcp-utility

Here is an additional article on using Entra auth with BCP in case you haven't run across it yet: https://learn.microsoft.com/en-us/sql/tools/bcp-utility?view=sql-server-ver16&tabs=windows

dlevy-msft avatar Aug 08 '24 15:08 dlevy-msft

not relevant for this repo

shueybubbles avatar Dec 30 '24 15:12 shueybubbles