Forum Discussion
Scheduled Refresh Failure on Report Server (May 2025) - IDbCommand interface exception
- 4 months ago
Hi FLORENTINO_23,
Thank you for the update, and we are glad to hear that your refresh issue has been resolved.
Based on our understanding, while using SELECT * followed by “Remove Other Columns” will work, it is considered best practice to explicitly select only the required columns in your SQL query. This improves performance, reduces data transfer, ensures better query folding, and helps avoid unexpected schema changes. Your current approach is acceptable for small datasets. However, for production scenarios, defining columns at the source is recommended.
Should you have any further questions, please feel free to contact the Microsoft Fabric community.
Thank you.
- FLORENTINO_235 months agoRegular Visitor
The report pulls from SQL and share-drive files. What additional details can I provide for you?
- tayloramy5 months agoSuper User
Hi FLORENTINO_23,
Do you have a gateway set up and configured properly? After you upload the report, are you going into the semantic model in Fabric and configuring the connections?