Version 1.5.5, released 2026-08-10. These files are mirrored from
GitHub release v1.5.5.20260810
and served from packages.clickhouse.com, so they can be
downloaded on networks where github.com is blocked.
| File | Platform | Size |
|---|---|---|
| clickhouse-odbc-1.5.5-win64-manual-install.zip | 2.1 MiB | |
| clickhouse-odbc-1.5.5-win64.msi | Windows (x86_64) | 2.3 MiB |
| clickhouse-odbc-linux-Clang-UnixODBC-Release.zip | Linux (x86_64) | 51.9 MiB |
| clickhouse-odbc-macos-AppleClang-UnixODBC-Release.zip | macOS | 19.1 MiB |
aba89627e2e7c9fa7af09a6d9f0ceff2c9960897773c067d2e742e1cef1775a9 clickhouse-odbc-1.5.5-win64-manual-install.zip
35d65f3c60d3a227978de229f3745281009805c23e90777f0b7512a9d88edb00 clickhouse-odbc-1.5.5-win64.msi
a3a43bc0a4a53048533f75c592c8cbea967c99f474baaee50cc5e49968cc064e clickhouse-odbc-linux-Clang-UnixODBC-Release.zip
a8cea420e6ba00fc4a52c11d64feddc7b41f94bc8b4a19ebd0a599545cc7a601 clickhouse-odbc-macos-AppleClang-UnixODBC-Release.zip
Also available as /odbc/sha256sums.txt, in
sha256sum -c format.
Install the driver with the MSI, silently or interactively:
msiexec /i clickhouse-odbc-1.5.5-win64.msi /qn
Enterprise packaging systems (SCCM, Intune, Tanium, BigFix, ...) often repackage third-party software instead of running vendor installers. The MSI's payload can be extracted without installing anything:
msiexec /a clickhouse-odbc-1.5.5-win64.msi /qb TARGETDIR=C:\clickhouse-odbc
That writes the driver files under C:\clickhouse-odbc; the two
DLLs you need are clickhouseodbc.dll (ANSI) and
clickhouseodbcw.dll (Unicode). Copy them to their final location,
then register them with the template below, which reproduces exactly the
registry entries the MSI would have written:
reg import clickhouse-odbc.reg from an elevated promptThere is currently no separate portable ZIP for Windows — the MSI is the only Windows artifact the driver publishes.
The Linux archive contains a .tar.gz and a .tar.xz
of the same tree, each with its own .sha256 file:
curl -fO https://packages.clickhouse.com/odbc/clickhouse-odbc-linux-Clang-UnixODBC-Release.zip
unzip clickhouse-odbc-linux-Clang-UnixODBC-Release.zip
sha256sum -c clickhouse-odbc-1.5.5-Linux.tar.gz.sha256
tar -xzf clickhouse-odbc-1.5.5-Linux.tar.gz
sudo cp clickhouse-odbc-1.5.5-Linux/lib/libclickhouseodbc*.so /usr/local/lib64/
Register the driver with unixODBC. The
share/doc/clickhouse-odbc/config/ directory in the archive holds
ready-made samples:
odbcinst -i -d -f clickhouse-odbc-1.5.5-Linux/share/doc/clickhouse-odbc/config/odbcinst.ini.sample
odbcinst -i -s -l -f clickhouse-odbc-1.5.5-Linux/share/doc/clickhouse-odbc/config/odbc.ini.sample
Or add this to /etc/odbcinst.ini by hand, fixing the paths if
you installed the libraries elsewhere:
[ODBC Drivers]
ClickHouse ODBC Driver (ANSI) = Installed
ClickHouse ODBC Driver (Unicode) = Installed
[ClickHouse ODBC Driver (ANSI)]
Description = ODBC Driver (ANSI) for ClickHouse
Driver = /usr/local/lib64/libclickhouseodbc.so
Setup = /usr/local/lib64/libclickhouseodbc.so
UsageCount = 1
[ClickHouse ODBC Driver (Unicode)]
Description = ODBC Driver (Unicode) for ClickHouse
Driver = /usr/local/lib64/libclickhouseodbcw.so
Setup = /usr/local/lib64/libclickhouseodbcw.so
UsageCount = 1
Same layout as Linux, with .dylib libraries, and configuration
under /Library/ODBC/ (system-wide) or
~/Library/ODBC/ (per user):
curl -fO https://packages.clickhouse.com/odbc/clickhouse-odbc-macos-AppleClang-UnixODBC-Release.zip
unzip clickhouse-odbc-macos-AppleClang-UnixODBC-Release.zip
shasum -a 256 -c clickhouse-odbc-1.5.5-Darwin.tar.xz.sha256
tar -xJf clickhouse-odbc-1.5.5-Darwin.tar.xz
sudo cp clickhouse-odbc-1.5.5-Darwin/lib/libclickhouseodbc*.dylib /usr/local/lib/
A data source needs, at minimum, the driver and a URL:
[ClickHouse DSN (Unicode)]
Driver = ClickHouse ODBC Driver (Unicode)
Url = https://username:password@your-host:8443/query?database=default
The full list of DSN parameters — Server,
Port, Database, SSLMode,
Compression, Timeout, driver logging, and the rest
— is in the driver documentation:
github.com/ClickHouse/clickhouse-odbc. Prefer the Unicode driver unless an
application specifically requires the ANSI one.