Snowflake Download Odbc Driver Fix
Sixta Strissel
If you are already using the ODBC driver and need to download an updated version, check the version that you are using, andreview the changes between your version and the updated version in the ODBC Driver release notes
To find the version of the driver that you are using, call the CURRENT_CLIENT SQL function froman application using the driver. You can also verify the driver version byexamining queries executed by the driver in the QUERY_HISTORY view.
My Snowflake driver is installed to /opt/snowflake/snowflakeodbc, so that is correct -- I'm suspicious that this is specifically an M1 problem. I'm using the 2.24.1 version of the driver available from the download mirror here, and the path to the driver in /etc/odbcinst.ini is /opt/snowflake/snowflakeodbc/lib/universal/libSnowflake.dylib (which exists and seems, from all my research, that it should be right).
You need to point the Snowflake driver towards the iODBC dylib (as per a sideswiping statement in the docs) -- the driver is originally configured to look for the ODBC dylib (not iODBC) in a folder that's on the path.
When you install the iODBC driver, verify that it is installed to /usr/local/iODBC (this was where my Silicon Mac installed it to) -- and that /usr/local/iODBC/lib has libiodbc.dylib in it. If so, navigate to your installed snowflake driver directory (should be /etc/snowflake) and alter the simba.snowflake.ini file (/etc/snowflake/snowflake/snowflakeodbc/universal/simba.snowflake.ini). You want to uncomment & alter the last line to be both uncommented & point with a full path towards the iODBC dylib (instead of the default, which is the ODBC dylib).
It seems like the core of the issue is that the odbc code is looking for arm64 architecture drivers but Snowflake is providing it in x86_64 architecture. By installing an x86_64 versions of odbc we are able to have it successfully talk to the driver.
Has anyone gotten this to work? I use excel w odbc to refresh snowflake files and have tried multiple ways to move the drivers etc and followed snowflake instructions but never works. I did get parallels to work running windows arm but would prefer to just do this in Mac OS
I also have a M1 (version Monterey 12.0) and I ran into similar issues when I tested the driver. Nevertheless, when I tried the "real connection" it worked like a charm. So, maybe it would be good for you to go and test the "real connection" to avoid a wasting of time using such testing. Hope you find this useful.
Recently I received a request to integrate a connection with an existing Rails application. After some research I came to the conclusion that one of the only ways to query the Snowflake views was through an ODBC connection using a combination of -odbc and
With this file updated with your Snowflake information you can now test the connection using the following command that is included with iODBC:
/Library/Application Support/iODBC/bin/iodbctest
This will allow you to enter an iODBC connection string for any of the DSNs listed using the ? command. This connection string should not be enclosed in quotes and should be in the following format:
Now, that was a lot of setup just to get to a prompt where you are able to query Snowflake. Now that you have all of that working you would expect to be able to install the ruby-odbc gem and start working in your Rails environment. When you go to install the ruby-odbc gem you will run into an error:
Our ODBC driver is a standalone installation file that doesn't require the user to deploy and configure any additional software such as a database client or a vendor library. Deployment costs are reduced drastically, especially when using the silent install method with an OEM license in large organizations that have hundreds of machines.
With our fully Unicode-compliant driver, you can properly retrieve and modify any data in multilingual Snowflake databases, regardless of their character set: Latin, Cyrillic, Hebrew, Chinese, etc., and in any language environment.
Next, open the configuration file (e.g. /opt/snowflake/snowflakeodbc/lib/simba.snowflake.ini) in the folder where you installed the Snowflake driver. You may need administrator privileges to edit the file.
Then add ODBCInstLib=/opt/homebrew/lib/libodbcinst.dylib to the end of the configuration file. (This path will vary depending on where you have installed homebrew, so please check the path of homebrew installed on your Mac.)
Locate DriverManagerEncoding at the top of the same configuration file (e.g. /opt/snowflake/snowflakeodbc/lib/simba.snowflake.ini). The default may be UTF-32, in which case change it to UTF-16 and save it as follows.
If the path /opt/snowflake/snowflakeodbc/lib/universal/cacert.pem is specified for the CABundle in your environment and this file path does not exist, specify an appropriate file path (for example, remove the universal part, If the path universal/cacert.pem is specified in the CABundle and this file path does not exist, you will need to specify the appropriate file path (for example, remove the universal part).
HVR requires that the Snowflake ODBC driver is installed on the machine from which HVR connects to Snowflake. For more information on downloading and installing Snowflake ODBC driver, see Snowflake Documentation.
After installing the Snowflake ODBC driver, configure the LogLevel configuration parameter as specified in ODBC Configuration and Connection Parameters of the Snowflake Documentation.
For a default installation, these files are available at /etc and do not need to be specified. However, when UnixODBC is installed in for example /opt/unixodbc the value for this field would be /opt/unixodbc/etc.
HVR uses the Snowflake ODBC driver to write data to Snowflake during continuous Integrate and row-wise Refresh. However, the preferred methods for writing data to Snowflake are Integrate with /Burst and Bulk Refresh using staging as they provide better performance (see section 'Burst Integrate and Bulk Refresh' below).
As a pre-requirement, the Snowflake connector requires users to install the Snowflake ODBC driver in their machines, matching the architecture of the Power BI Desktop installation (i.e. 32-bit vs. 64-bit). The Snowflake ODBC driver can be downloaded from this location: =823762
ODBC problems with Snowflake. Set up latest Snowflake driver in system DNS (64-bit). Tested successfully. Accessed through ODBC in Excel, so i know it works. Set up in Easymorph. Tested successfully (see Capture1). Tried to query. Get ERROR [22000] message (see Capture 2).
In an effort to keep current with bug fixes in the Snowflake driver, SAS has updated the current Snowflake driver to 2.25.11. The libcurl library was updated from 7.87.0 to 7.88.1 and the zlib library was updated from version 1.2.11 to 1.2.13.
When first searching for a way to connect to Snowflake from R I found a coupleof posts where it looked fairly easy to do exactly that.One was from Martin Stingl on his rstats-tips blog(highly recommended). And I also found a post on community.snowflake.comtitled How To Connect Snowflake with R/RStudio using ODBC driver on Windows/MacOS/Linux.This too easy how to article consisted of 2 steps:
Currently there are 4 open issues in the r-dbi/odbc repository dealing with what I assumeis the same issue. Just 2 days ago Sharon Wang has created a PR that addresses this as well (thanks a lot ?).
People have offered solutions that were helpful for some persons.The sad thing however was that none of the posts have helped me with finding a solution.I have already come to terms with it and on the plus side highly improved my SQL skills?. But today I sat down at my desk, had a coffee and checked againthese open odbc issues and found this new comment from Sharon Wang:
That somehow rang a bell which led me to this stackoverflow posttitled How do I install the ODBC driver for Snowflake successfully on an M1 Apple Silicon Mac?The second most upvoted answer from Scott Brenstuhlfinally gave me the solutionand I was able to connect to Snowflake.This is basically what I had to do:
After the driver has been installed, find the file, simba.snowflake.ini (usually located in \usr\lib64\snowflake\odbc\simba.sbowflake.ini). If you do not know where the file is installed, run the command:
MicroStrategy does not support the creation of connections using a JDBC driver. However, MicroStrategy Web supports the creation of connections using the ODBC driver, as explained in the ODBC tab of this page.
Kissflow BI connector allows you to access your Kissflow data stored in a Snowflake database with Microsoft Power BI via the ODBC driver. The ODBC driver acts as the interface for Microsoft Power BI to connect to Snowflake. By setting up this connection, you can access and analyze your Kissflow data in Microsoft Power BI.
To enable the ODBC connection for the Kissflow connector, you need to download and install the Snowflake ODBC driver in your Windows machine . Learn to download the Snowflake ODBC driver from the Snowflake website.
Devart ODBC Driver for Snowflake is a high-performance solution with enterprise-level functionality that allows connecting to Snowflake easily. Using our driver, you can connect fast to Snowflake from different analytics, reporting, BI, or ETL applications that are ODBC-compliant from both 32-bit and 64-bit Windows. ODBC driver fully covers standard ODBC API methods and data types and offers safe and simple access to real-time Snowflake data from any location.
Utilizing our ODBC driver, you may integrate Snowflake objects like regular SQL tables into your data infrastructure. All the advantages of SQL may be used in SELECT queries that are compatible with SQL-92 thanks to the enhanced SQL syntax:
The ODBC driver for Snowflake is completely Unicode. You can accurately extract and deal with data from multilingual Snowflake databases, regardless of the charset used (Latin, Cyrillic, Hebrew, Chinese, etc.) or the localization of your working environment.
df19127ead