Let’s be honest. You didn’t wake up this morning thinking, “I really hope I get to configure a data source name today.”
Now go connect something.
| 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) | 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.
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. Let’s be honest
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.
Go open odbcad32.exe right now. Look at your System DSNs. If that list is empty, you have work to do. | You need this driver
# Install unixODBC via Homebrew brew install unixodbc brew install msodbcsql18 Configure it manually (the fun part) nano /usr/local/etc/odbcinst.ini