iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
To install Microsoft ODBC Driver 17 for SQL Server on Windows 11, download the installer that matches the architecture of the application that will use it. A 64-bit program needs the x64 driver; a 32-bit program needs the x86 driver, even when Windows itself is 64-bit.
The current generally available Windows release is Driver 17.11.1.1, shown as 17.11.1 on Microsoft’s download page. Driver 17 can be installed alongside Driver 18, so installing Driver 18 does not automatically satisfy an application that explicitly requests ODBC Driver 17 for SQL Server.
Before you install
Check these two requirements first:
| Application that will use ODBC | Driver package |
|---|---|
| 64-bit application | ODBC Driver 17 for SQL Server (x64) |
| 32-bit application on 64-bit Windows | ODBC Driver 17 for SQL Server (x86) |
| 32-bit Windows | ODBC Driver 17 for SQL Server (x86) |
The driver architecture must match the application, not merely the Windows installation. For example, a 32-bit accounting program cannot use the driver installed by the x64 package.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →The driver also requires the matching Microsoft Visual C++ Redistributable. Install the current Visual C++ Redistributable from Microsoft if it is not already installed. Use x64 for a 64-bit application and x86 for a 32-bit application. On 64-bit Windows, it is normal to install both redistributables when both types of software need support.
#1 Best Overall
- The Anker Advantage: Join the 50 million+ powered by our leading technology.
- Enhanced Durability: Improved construction techniques and materials make a cable that lasts 5× longer.
- Universal Compatibility: Designed to work flawlessly with any device that uses a USB-C port.
- Fast Sync & Charge: Supports fast charging up to 15W (3A/5V) and data transfer speeds up to 480Mbps. (Not compatible with Power Delivery).
- What You Get: 2 × Premium Nylon-Braided USB-A to USB-C Charger Cable (3ft), welcome guide, everlasting warranty, and our friendly customer service.
Download ODBC Driver 17
- Open Microsoft’s ODBC Driver for SQL Server download page.
- Scroll to the Version 17 section.
- Select Download Microsoft ODBC Driver 17 for SQL Server (x64) or Download Microsoft ODBC Driver 17 for SQL Server (x86).
- Save the downloaded
msodbcsql.msifile.
Do not assume that the x64 download installs the 32-bit driver as well. Microsoft supplies separate Driver 17 installers for the two architectures.
Install it with the graphical setup
- Open the downloaded
msodbcsql.msifile. - Approve the User Account Control prompt by selecting Yes.
- Select Next in the setup wizard.
- Read the license terms, select I accept the terms in the license agreement, and select Next.
- Leave the default features selected unless your organization uses a specific application-packaging policy.
- Select Install.
- Select Finish when setup completes.
Current Driver 17.11 setup installs both the Core and SDK features by default. Older instructions may describe a different default feature selection.
Install from Command Prompt
Open Command Prompt as an administrator and change the path to the location of your MSI file. To install all features interactively, run:
Recommended Free Tools
msiexec.exe /i "C:UsersYourNameDownloadsmsodbcsql.msi" ADDLOCAL=ALLFor an unattended installation, accept the license explicitly:
msiexec.exe /quiet /qn /i "C:Pathmsodbcsql.msi" IACCEPTMSODBCSQLLICENSETERMS=YES ADDLOCAL=ALLThe license property must be written in uppercase when using quiet or other noninteractive options such as /passive, /qb, or /qr.
Rank #2
- Fit for PS4 controller, DualShock 4, PS4 Slim/Pro, and Xbox One controllers (for Xbox Elite Wireless Controller models 1537, 1697, 1708, 1698). Fit for Kindle Gen 2-10 (2009-2019), Kindle Paperwhite Gen 5-10 (2012-2018), Kindle Oasis, Voyage, DX, Touch. Fit for Amazon Kindle Tablet Fire 7 (2017/2019), Fire HD 8 (2015/2017/2018), Fire HD 10 (2015/2017)
- Fit for Roku Streaming Stick 3500X, 3600X, 3800X, Streaming Stick 4K/4K+ 3820R, 3820R2, 3820X, 3820X2, 3821R, 3821R2, 3821X, 3821X2, Express 3700X, 3700R, 3900X, 3930X, 3930EU, 3930R, 3930S4, 3930RW, 3932X, 3932RD, 3940X, 3940X2, 3940RW, 3940CA2, 3960X, 3960R, Express+ 3710X, 3910X, 3910RW, 3931X, 3931RW, 3941X, 3941X2. Fit for Premiere 3920X, 3920R, 3920RW, Premiere+ 3921X Express 4K+. Fit for Fire TV Stick 1st 2nd Gen, Fire TV Stick Lite, Fire TV Stick Basic Edition, Fire TV Stick 4K Max
- Compatibility notice!! This Micro-USB cable is not compatible with USB-C devices or controllers, such as PS5 DualSense, Xbox Series X/S (Models 1914 and 1797), Xbox 360, Roku Ultra, and Fire TV Cube. Not fit for Kindle with a USB-C connector. Please double-check your device’s port before purchasing
- 24 months manufacturer warranty
- Supports fast 2A charging and 480 Mbps data transfer with 22 AWG low-impedance wires — safe, stable, and built for long-term performance
To create a detailed Windows Installer log while troubleshooting:
msiexec.exe /i "C:Pathmsodbcsql.msi" IACCEPTMSODBCSQLLICENSETERMS=YES ADDLOCAL=ALL /L*v "C:TempODBC17-install.log"Make sure C:Temp exists before running the command. The log can identify missing prerequisites, permission problems, and installer rollback conditions.
Verify the installation
Check the Drivers tab
- Open Start and search for ODBC Data Sources.
- Choose the administrator matching your application: ODBC Data Sources (64-bit) or ODBC Data Sources (32-bit).
- Open the Drivers tab.
- Confirm that the list contains
ODBC Driver 17 for SQL Server.
On 64-bit Windows, the administrator programs are located at:
C:WindowsSystem32odbcad32.exe
C:WindowsSysWOW64odbcad32.exeDespite the directory names, System32 contains the 64-bit ODBC Administrator and SysWOW64 contains the 32-bit ODBC Administrator.
Check the installed files
The main 64-bit Driver 17 file is normally:
%SYSTEMROOT%System32msodbcsql17.dllThe diagnostics library is normally %SYSTEMROOT%System32msodbcdiag17.dll. A file being present is not sufficient proof that all dependencies load, so the Drivers tab or a real connection test is the more useful verification.
Rank #3
- Durable Design: Reinforced nylon exterior and a robust core ensure this cable withstands up to 5,000 bends, outlasting other brands
- Fast Charging: Supports Power Delivery for up to 60W high-speed charging when paired with a USB-C charger
- Versatile Compatibility: Works with virtually all USB-C devices, including phones, tablets, and laptops
- High-Speed Data Transfer: Transfer files quickly with 480Mbps data transfer speeds
- Included Accessories: Comes with a hook-and-loop cable tie for easy organization and a welcome guide for hassle-free setup
Use Driver 17 in a connection string
The driver name in a DSN-less connection string must match the installed name exactly:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Driver={ODBC Driver 17 for SQL Server};Server=serverName;Database=databaseName;Trusted_Connection=Yes;For SQL authentication, an application might instead use:
Driver={ODBC Driver 17 for SQL Server};Server=serverName;Database=databaseName;Uid=userName;Pwd=password;The legacy driver name SQL Server is not the same driver. Changing the connection string to ODBC Driver 17 for SQL Server is necessary when the application is intended to use Driver 17.
Create a DSN
- Open the 32-bit or 64-bit ODBC Administrator that matches the application.
- Select User DSN or System DSN.
- Select Add.
- Choose ODBC Driver 17 for SQL Server.
- Select Finish.
- Enter the SQL Server name, authentication details, and database settings requested by the wizard.
- Save the data source and test it from the application.
Use a System DSN for a Windows service or another application that runs under a different account from the user who created the DSN. A 32-bit application must use a DSN created in the 32-bit administrator; a 64-bit application must use one created in the 64-bit administrator.
Troubleshoot common installation problems
The driver is missing from the Drivers tab
Open both administrators directly:
C:WindowsSystem32odbcad32.exe
C:WindowsSysWOW64odbcad32.exeIf Driver 17 appears in only one, that is expected when only one architecture was installed. Install the other MSI if the application needs it. If it appears in neither, check whether the MSI completed successfully and install the matching Visual C++ Redistributable before trying again.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Rank #4
- 6.6ft Freedom – No More Port Strain: Short 3FT cables yank your USB ports, forcing hard drives and cooling pads into awkward spots. Over time, that tugging damages ports. This 6.6FT USB A to USB A cable gives you slack to route cleanly across any desk, reach a floor KVM, or connect a distant hub. Place devices where they belong, not where a short USB to USB cable dictates. Zero port stress.
- Never Rupture & Nylon Braided – Hydrophobic & Anti-Pilling: Unique SR anti-break design, tested 400,000+ bends for extreme durability. Sturdy dual-shade braided nylon jacket of the USB-A to USB-A cable offers stronger protection, flexibility, anti-pilling, and tangle resistance. Hydrophobic nylon layer repels water and resists sticky residue — spilled drinks won't affect connection. No cable breakage worries, even on messy desks.
- 5Gbps Data Transfer Speed – 9-Core Tinned Copper: Transfer large files in seconds with 5Gbps speed, 10x faster than USB 2.0. Inside: a premium 9-core tinned copper matrix with triple shielding (foil+braid) blocks EMI/RFI interference for signal clarity. The 24K gold-plated connectors of the USB to USB cable ensure stable, oxidation-resistant conductivity for many years. Backward compatible with USB 2.0/1.1 ports.
- Huge Output For Your Cooling Pad: The maximum output of this USB A to USB A male to male USB 3.0 cable is up to 3A, providing enough power for your laptop cooler to perform at its best. No more worry about your laptop getting hot — ensures stable operation of your devices without low-power lag.
- Wide Compatibility: Connects USB peripherals with USB 3.0 Type-A port to a computer for speedy file transfer. Compatible with Laptop, Laptop Cooling Pad, Smart TV, USB in car, DVD player, USB 3.0 hub, Monitor, KVM, Camera, Wacom, Blu-ray Drive, Set Top Box, 2.5-Inch External Hard Drive Enclosure, and most USB 3.0 external hard drives with Type-A port.
IM002: Data source name not found and no default driver specified
This usually means one of three things: the DSN is in the other architecture’s ODBC Administrator, the application cannot see the installed driver, or the connection string names a driver that is not installed. Check that:
- The DSN exists in the correct administrator.
- The application and driver have the same architecture.
- The connection string says exactly
ODBC Driver 17 for SQL Server. - The driver appears on the correct Drivers tab.
- The driver DLL and its Visual C++ dependencies can load.
Setup says that a restart is required
Close SQL Server Management Studio, Visual Studio, SQL Server Profiler, and other programs that may be using the driver. If the message continues, open Control Panel > Programs and Features, uninstall Microsoft ODBC Driver 17 for SQL Server, restart Windows if prompted, and rerun the installer. This is particularly relevant when another Microsoft product is installing or updating the same driver.
An old Driver 17 installation blocks the upgrade
Microsoft specifically advises manually uninstalling Driver 17.1.0.1 or earlier before installing a newer package. For ordinary current Driver 17 installations, the newer package should upgrade the existing Driver 17 installation.
The installation is damaged or another installer reports missing components
Open Settings > Apps > Installed apps, find the Microsoft ODBC Driver 17 entry, and choose Modify when available. Reinstalling the current Driver 17 MSI is also appropriate. Do not uninstall a working Driver 17 solely because SQL Server or another product contains an older bundled copy; first determine which version that product is trying to use.
Uninstall Driver 17
For a normal removal, open Settings > Apps > Installed apps, search for Microsoft ODBC Driver 17 for SQL Server, select the three-dot menu, and choose Uninstall.
Best Value
- IN THE BOX: (1) 6-foot high-speed multi-shielded USB 2.0 A-Male to B-Male cable
- DEVICE COMPATIBLE: Connects mice, keyboards, and speed-critical devices, such as external hard drives, printers, and cameras to a computer
- ULTRA FAST SPEED: Full 2.0 USB capability with 480 Mbps transfer speed
- DURABLE DESIGN: Corrosion-resistant, gold-plated connectors for optimal signal clarity and shielding to minimize interference
If you still have the original MSI, a quiet uninstall can be run with:
msiexec.exe /quiet /qn /uninstall "C:Pathmsodbcsql.msi"Removing the driver can break applications whose connection strings explicitly request Driver 17, so check application requirements before uninstalling it.
FAQ
Is ODBC Driver 17 compatible with Windows 11?
Microsoft’s compatibility information lists ODBC Driver 17.10 as supported on Windows 11. The current Windows download is the later 17.11.1.1 release, so use Microsoft’s current Driver 17 package rather than an old archived installer.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteDoes installing the x64 driver install the 32-bit driver too?
No. Driver 17 has separate x64 and x86 installers. Install the x86 package for a 32-bit application, even on 64-bit Windows.
Can Driver 17 and Driver 18 be installed together?
Yes. They are separate side-by-side drivers. An application that specifies ODBC Driver 17 for SQL Server continues to request Driver 17.
Does the ODBC driver install sqlcmd.exe?
No. sqlcmd.exe and bcp.exe are separate Microsoft Command Line Utilities downloads. They use the ODBC driver but are not installed by the Driver 17 MSI.
Which ODBC Administrator should I use?
Use C:WindowsSystem32odbcad32.exe for 64-bit applications and C:WindowsSysWOW64odbcad32.exe for 32-bit applications on 64-bit Windows.
Free tools Windows power users keep installed
One-click scans. No signup required.
The Bottom Line
Download Driver 17 from Microsoft’s Version 17 section, select x64 or x86 according to the application, install the matching Visual C++ Redistributable if necessary, and verify the exact name ODBC Driver 17 for SQL Server in the correct ODBC Administrator. Most connection errors after installation are caused by using the wrong administrator, wrong driver architecture, or an inexact driver name.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
