| If you need to connect to... | You need this driver... | |----------------|--------------------------| | | ODBC Driver 17/18 for SQL Server (Microsoft) | | PostgreSQL | psqlODBC | | MySQL | MySQL Connector/ODBC | | Oracle | Oracle ODBC Driver (painful, but works) | | Snowflake/BigQuery | Vendor-specific ODBC drivers (usually decent) | | Excel/Access | Built into Windows (Microsoft Access Driver) |
# Install unixODBC via Homebrew brew install unixodbc brew install msodbcsql18 Configure it manually (the fun part) nano /usr/local/etc/odbcinst.ini how to install odbc
That bridge is (Open Database Connectivity). And installing it isn't hard—but doing it right so you don't cry at 2 AM? That’s an art. | If you need to connect to
Inside odbcinst.ini :
You’re here because Tableau won’t connect to your legacy ERP system. Or because Python keeps throwing a Data source name not found error. Or because your boss sent you a CSV file that lives inside a SQL Server database, and now you have to build a bridge. And installing it isn't hard—but doing it right
[ODBC Driver 18 for SQL Server] Description=Microsoft ODBC Driver 18 for SQL Server Driver=/usr/local/lib/libmsodbcsql.18.dylib Then configure odbc.ini for your DSN. Same as macOS but with apt or yum . The pain is equal, just different package names. Step 3: Creating the DSN (Where The Magic Happens) A DSN is just a saved shortcut. "NorthwindDB" is easier to type than Server=192.168.1.105;Database=Sales;UID=bob;PWD=hunter2 .
But it is everywhere . Every BI tool, every ETL platform, every scripting language that talks to databases (R, Python, PHP, Perl) eventually falls back to ODBC.