Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Vote for your favorite vizzies from the Power BI Dataviz World Championship submissions. Vote now!
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.
Vote for your favorite vizzies from the Power BI World Championship submissions!
If you love stickers, then you will definitely want to check out our Community Sticker Challenge!
Check out the January 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 63 | |
| 50 | |
| 41 | |
| 19 | |
| 16 |
| User | Count |
|---|---|
| 125 | |
| 108 | |
| 46 | |
| 29 | |
| 27 |