ODBC connector
Introduction
The Microsoft Open Database Connectivity (ODBC) interface allows applications/clients to use Structured Query Language (SQL) to access data in the data platform. The ODBC clients provide access to data on Windows, Linux®, and macOS servers. The ODBC interface is certified to be compatible with leading analysis and reporting applications such as Tableau, Microsoft Excel, and many more. As of 2023, the ODBC connector on the Data Platform will replace the former Veryant ODBC connector that could be used directly on ANVA 4/5. The Veryant ODBC connector is end-of-life, no longer supported, and its use is no longer permitted.
Features Data Platform-ODBC
- SQL-92 access to the data platform.
- Connect with live data from the data platform (ANVA 4/5 and Hub), for real-time data access.
- Data aggregation and complex JOINs in SQL queries.
- Secure connectivity with modern cryptography, including TLS 1.2, SHA-256, ECC, etc.
Specifications
- Support 32-bit and 64-bit applications.
- Native protocol-based drivers compliant with ODBC 3.8.
- Comprehensive ANSI SQL-92 support.
- Full Unicode Support - any language - all data.
- Cross-platform ODBC. Available for Windows, Linux® and macOS.
Technical Documentation
ODBC access requires downloading an ODBC connector from the Snowflake website. The Snowflake Web site also provides a detailed description for installing the ODBC connector.
It is recommended to install the 64-bit version of the ODBC connector for this purpose. This version functions better for tables with large volumes.
Download site: https://developers.snowflake.com/odbc/
Installing and configuring the ODBC connector is described on Snowflake's website: https://docs.snowflake.com/en/user-guide/odbc.html
More information regarding setup in SQL server Management studio: https://snowflakecommunity.force.com/s/article/how-to-set-up-a-linked-server-from-sql-server-to-snowflake
https://www.mssqltips.com/sqlservertip/6679/sql-server-linked-server-to-snowflake/
For access, ANVA provides a private key file with a strong password, these must be set up when configuring the ODBC connector.
The private key file should preferably be stored in a location where as few people as possible have access.

