@rahul_goyal
This is a common point of confusion when setting up Snowflake federation in Databricks, so let me clarify what is happening.
SHORT ANSWER
The JDBC URL display showing "jdbc://" instead of "jdbc❄️//" is expected behavior and is not a defect. Databricks internally constructs the proper Snowflake JDBC connection using the host and port you provide. The URL shown in the UI is a simplified display representation, not the actual JDBC connection string used behind the scenes.
As the other responder confirmed, connections work correctly despite how the URL appears in the interface.
HOW DATABRICKS HANDLES THE SNOWFLAKE CONNECTION
When you create a Snowflake connection through Lakehouse Federation, you do not provide a full JDBC URL yourself. Instead, you provide individual connection parameters:
- Host (e.g., dyjcxbz-gfc45507.snowflakecomputing.com)
- Port (443)
- Authentication credentials (OAuth, username/password, PEM key, etc.)
Databricks takes these parameters and internally builds the correct JDBC connection to Snowflake. The "jdbc://" format you see displayed in the UI is just how the connection metadata is shown -- it is not the literal JDBC string passed to the Snowflake JDBC driver.
VERIFYING YOUR CONNECTION ACTUALLY WORKS
If you want to confirm your connection is working properly, here are the steps:
1. After creating the connection, create a foreign catalog:
CREATE FOREIGN CATALOG my_snowflake_catalog
USING CONNECTION my_snowflake_connection
OPTIONS (database '<your-snowflake-database-name>');
2. Then try querying a table:
SELECT * FROM my_snowflake_catalog.schema_name.table_name LIMIT 10;
3. You can also test the connection in Catalog Explorer by clicking on the connection and using the "Test connection" button.
If you are getting an actual error when trying to query data through the connection (not just concerned about the URL display), please share the exact error message -- that would help narrow down whether there is a real connectivity issue vs. just a UI display concern.
COMMON SNOWFLAKE FEDERATION ISSUES TO CHECK
If you do run into actual connection failures, here are things to verify:
- Network connectivity: Your Databricks workspace must be able to reach your Snowflake account endpoint on port 443.
- Authentication: If using OAuth, make sure you created the security integration in Snowflake with the correct redirect URI pointing to your workspace URL.
- Case sensitivity: If your Snowflake database name is case-sensitive, wrap it in double quotes when creating the foreign catalog, for example:
CREATE FOREIGN CATALOG my_catalog
USING CONNECTION my_connection
OPTIONS (database '"MyDatabase"');
- Compute requirements: You need Databricks Runtime 13.3 LTS or above, or a Pro/Serverless SQL warehouse (version 2023.40+).
DOCUMENTATION REFERENCES
Full Snowflake federation setup guide:
https://docs.databricks.com/en/query-federation/snowflake.html
Lakehouse Federation overview (query federation vs. catalog federation):
https://docs.databricks.com/en/query-federation/index.html
CREATE CONNECTION SQL reference:
https://docs.databricks.com/en/sql/language-manual/sql-ref-syntax-ddl-create-connection.html
Hope this helps clarify things. If you are seeing an actual error message when testing or querying through the connection, please share it and we can dig deeper.
* This reply used an agent system I built to research and draft this response based on the wide set of documentation I have available and previous memory. I personally review the draft for any obvious issues and for monitoring system reliability and update it when I detect any drift, but there is still a small chance that something is inaccurate, especially if you are experimenting with brand new features.
* This reply used an agent system I built to research and draft this response based on the wide set of documentation I have available and previous memory. I personally review the draft for any obvious issues and for monitoring system reliability and update it when I detect any drift, but there is still a small chance that something is inaccurate, especially if you are experimenting with brand new features.
