โ07-28-2025 04:07 AM
โ07-28-2025 05:05 AM - edited โ07-28-2025 05:34 AM
Maybe SQL Editor resolves column names in a different way compared to regular notebook. Anyway, if I were you I would check first how this attribute was defined in Snowflake.
If it was defined using unquoted identifier, like below
CREATE TABLE employee(employeeid INT)
Then this attribute will be stored and resolved in uppercase.
If your table attribute was defined using double-quoted identifier then it will preserve case-sensitivity, as you can see in following example from Snowflake documentation.
Now, if it was defined using double-quoted identifier then you have to use double quote as they suggest in databricks documentation, otherwise it won't work.
โ07-28-2025 04:13 AM - edited โ07-28-2025 04:22 AM
Hi @nkrom456 ,
Try something like this. If you are using backticks it treats a column name exactly as you type (in this case it treats double quotes as a part of a colum name)
create view vw_emp with schema binding as select `employeeid` from employee
OR
create view vw_emp with schema binding as select employeeid from employee
โ07-28-2025 04:25 AM
Hi Thanks for the prompt reply no its also not working the issue is federated table itself having column like "employeeid" with quotes so i have used backtick
โ07-28-2025 04:41 AM
Hi @nkrom456 ,
Thanks for clarification. Ok, so it looks like identifiers in Snowflake could be case-sensitive. So for example employeeid could be stored in Snowflake metadata as EMPLOYEEID. If that is the case you need to use double quotes to preserve the case. Could you try that?
Run federated queries on Snowflake (OAuth) | Databricks Documentation
โ07-28-2025 04:49 AM
Thanks a lot for the response. But the same query works on notebook only we are having issue with sql editor.
โ07-28-2025 05:05 AM - edited โ07-28-2025 05:34 AM
Maybe SQL Editor resolves column names in a different way compared to regular notebook. Anyway, if I were you I would check first how this attribute was defined in Snowflake.
If it was defined using unquoted identifier, like below
CREATE TABLE employee(employeeid INT)
Then this attribute will be stored and resolved in uppercase.
If your table attribute was defined using double-quoted identifier then it will preserve case-sensitivity, as you can see in following example from Snowflake documentation.
Now, if it was defined using double-quoted identifier then you have to use double quote as they suggest in databricks documentation, otherwise it won't work.
โ07-28-2025 08:33 AM
Thanks a lot . Yup I have checked the snowflake table and column names has double quotes, but when i executed the below query
โ07-28-2025 09:42 AM - edited โ07-28-2025 09:52 AM
Hi @nkrom456 ,
So this is exactly what I expected. You have a case-sensitive identifier then. But I think what they meant by double quotes is to use this character " and not specifying it double times like you did.
I don't have an access to snowflake to test it, but I think you should have something like this:
CREATE or replace VIEW vw_employee
WITH SCHEMA BINDING
AS select "employeeid" from "employee"
Passionate about hosting events and connecting people? Help us grow a vibrant local communityโsign up today to get started!
Sign Up Now