Snowflake JDBC connection help with RM Studio
CarlP
New Altair Community Member
Hi has anyone managed to connect RM studio 9.10 to Snowflake using JDBC? No matter what I try I can't seem to get this working. The instructions in the link below dont work and dont apply to v9.10 of RM
docs.rapidminer.com/latest/studio/connect/database/jdbc/
I would truly appreciate some help with this. thanks Carl
Tagged:
0
Best Answer
-
it worked after removing authenticator=externalbrowser&user=abc0
Answers
-
Hi @CarlP,
What exact settings did You tried to establish the connection?
I suggest to use a configuration like that:
After these setting you should provide the JDBC driver Jar file under the Driver tab.
Make sure you have installed Java 1.8 or higher on your local machine, due to this is a requirement for the Snowflake JDBC driver.
I hope this will help you out!
Cheers,
Bence
0 -
0 -
0
-
Based on the documentation the host url in this case should look like this: jea45817.us-east-1.snowflakecomputing.com , please remove the othe parts of the url.
0 -
RapidMiner 9.10.008 How to successfully connect using the Snowflake JDBC Driver. The 2 snapshots below show the proper way to configure RM 9.10 to Snowflake.
-1 -
snowflake connection success
0 -
I am getting the error No sutitable driver found for0
-
Hi shanila,
please make sure that the URL prefix is jdbc:snowflake://
See also this thread https://community.rapidminer.com/discussion/56737/how-to-resolve-no-suitable-driver-found-for-jdbc-snowflake-url-issue-when-connecting-to-snowflake
Greetings,
Jonas0 -
now i am getting a different error which is a number. !390190!
0 -
That's an Snowflake error code, does your Snowflake server require SAML / SSO?
You could try to add &authenticator=externalbrowser to the JDBC URL
Or check the ~/.RapidMiner/rapidminer-studio.log file for more details.0 -
Unfortunately i cant find log files
or am i looking in a wrong folder?
we have a trial version
we dont use SAML/SSO
this is how i connected
snowflake://abc.snowflakecomputing.com/?authenticator=externalbrowser&user=abc
0 -
it worked after removing authenticator=externalbrowser&user=abc0