This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreLevel up your Power BI skills this month - build one visual each week and tell better stories with data! Get started
I have a large SQL table in Snowflake where the column names are automatically generated and am having trouble using some, but not all of the volumns, in Power BI Desktop visuals, meaning I cannot, for instance, pull one of the columns into a Matrix to see the values.
One requirement is that I must use DirectQuery given the large size of the table. I also have Tableau and have noticed it is able to pull the same column data in without a problem so do not think there's an issue with the underlying SQL table.
Whenever I try to pull the problem fields in, I get the following error:
"Couldn't load the data for this visual"
Error message says "OLE DB or ODBC error: The command '[embedded SQL statement here]' isn't supported.."
I have found this appears to happen when column names exceed 128 characters. Is there a hard limit on the number of characters a column name can have? If so, is there a reason why this limit is so low?
Solved! Go to Solution.
Yes, that's what I ended up doing for now (though I did it on the SQL end to preserve consistency across files/applications) but not an ideal solution.
Yes, that's what I ended up doing for now (though I did it on the SQL end to preserve consistency across files/applications) but not an ideal solution.
@k-squared , You can rename the column in power bi. the source name will remain the same.
Check out the April 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 38 | |
| 29 | |
| 28 | |
| 20 | |
| 18 |
| User | Count |
|---|---|
| 66 | |
| 34 | |
| 31 | |
| 25 | |
| 23 |