ALTERYX INSPIRE | Join us this May for for a multi-day virtual analytics + data science experience like no other! Register Now
1 Day Left! - The Alteryx Community will be temporarily unavailable for a few hours due to implementation of the new SSO experience starting tomorrow at 5pm MDT. Please plan accordingly. For more information, read the blog.

Alteryx Designer Knowledge Base

Definitive answers from Designer experts.

How to download and install SQL Server ODBC drivers

How to download and install SQL Server ODBC drivers

This article will help provide instructions on how to download and install specific ODBC drivers. It is possible to have different ODBC driver versions side-by-side on a machine for maximum versatility to accommodate various environmental and compatibility needs.

  • Alteryx Designer
    • All versions
  • Alteryx Server
    • All versions
  • SQL Server ODBC drivers
    • ODBC 17
    • ODBC 13.1
    • ODBC Native Client 11
  • SQL Server
    • 2012
    • 2014
    • 2016
    • Azure SQL Database


ODBC 13.1

1. To download ODBC v13.1, click here.

2. Check the 64-bit file "x64\msodbcsql.msi" and click next to begin downloading.

3. Double-click the MSI file and follow the on-screen prompts to complete the install.

SQL Server Native Client 11

1. To download the Native Client 11, this is part of the "SQL Server® 2012 SP4 Feature Pack".

2. Click download and in the "Choose the download you want" prompt, check the file "sqlncli.msi" and click next. If there are two files, get the bigger one (approx 4.8 MB) in size.

3. Double-click the MSI file and follow the on-screen prompts to complete the install.

Common Issues

There have been various updates to ODBC 17 and Alteryx Designer has not been fully tested on ODBC 17. Check the SQL version compatibility matrix to best get the exact ODBC 17 driver version needed to accommodate your organization's environment (Database and Windows OS). Then all previous ODBC versions are accessible here with their release notes. If any issues are encountered within Alteryx Designer using a specific ODBC 17 driver version, test the ODBC 13.1 drivers to confirm the issue no longer exists, if possible.

Additional Resources