Forum Discussion
Scheduled Refresh Failure on Report Server (May 2025) - IDbCommand interface exception
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.
Latest Update: With the help of my IT team, some adjustments were made to the report server settings, and all my reports are now refreshing successfully. I truly appreciate your feedback pointing out it was a server-side issue rather than a DAX or file error, as everything worked fine locally.
Additionally, my IT team noted that my queries use SELECT * too frequently, followed by a 'Remove Other Columns' step. Should I specify the exact columns directly in the SQL query, or is my current method (Select * then remove columns) acceptable?