Forum Discussion
BUG: Cannot list tables in dbo schema when using Sybase Database connector
Hi ViliusS ,
Thank you for reaching out to us on the Microsoft Fabric Community Forum.
This is a known limitation with the Sybase Database connector in Power BI Desktop it only lists tables owned by the connecting user and often excludes shared schemas like dbo, even if the user has full DBA privileges.
To work around this issue, Use the ODBC connector instead of the native Sybase Database connector. The ODBC connector provides full visibility into all schemas and tables, including those in the dbo schema. To use it, first set up an ODBC DSN for your Sybase database or use a direct connection string. Then, in Power BI Desktop, go to Get Data > ODBC, select your configured DSN, and connect. I think by this way now be able to browse and access all available tables and schemas without restriction.
If this post was helpful, please give us Kudos and consider marking Accept as solution to assist other members in finding it more easily.
Thank you and Regards,
Menaka Kota.
Hi ViliusS ,
I completely understand your need to use the native Sybase Database connector, especially for performance reasons.
I’d recommend submitting this as a feature request. Appreciate if you could share the feedback on our Microsoft Fabric Ideas. Which would be open for the user community to upvote & comment on. This allows our product teams to effectively prioritize your request against our existing feature backlog and gives insight into the potential impact of implementing the suggested feature.
If this post was helpful, please give us Kudos and consider marking Accept as solution to assist other members in finding it more easily.
Thank you and Regards,
Menaka Kota.
I have created an idea https://community.fabric.microsoft.com/t5/Fabric-Ideas/Allow-to-view-dbo-schema-in-Sybase-Database-connector/idi-p/4676967#M160613 but it's not really idea/feature. It's a bug. Microsoft needs to prioritize bugs differently than just going through the list of "ideas". I suspect Sybase connector just has a dbo schema filter hardcoded in, so somebody just needs to remove that filter and fix this bug.