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!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
HI All, I am getting the below error while refreshing the dataset on POwer Bi Service. Its getting refreshed in desktop. I have also configured the incremental refresh but it seems its not working.
I have power Bi premium per user license.
Database connected to azure sql
PBIX file is 2 GB
Error Message
"
<pii>DataSource.Error: <pii>Microsoft SQL</pii>: <pii>Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.</pii>. DataSourceKind = <pii>SQL</pii>. DataSourcePath = <pii>24seven.database.windows.net;D365</pii>. Message = <pii>Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.</pii>. ErrorCode = <pii>-2146232060</pii>. Number = <pii>-2</pii>. Class = <pii>11</pii>. </pii>. The exception was raised by the IDbCommand interface."
Please help |
Solved! Go to Solution.
Hi, @Ballabh ;
Query timeout: The reason a command/query runs longer than expected is commonly due to blocking or the need for query/index tuning or bot.
Firstly, based on this blog, in Power BI Service, refreshing the dataset will give an error message letting you know your dataset is too large, and it will fail to refresh until you filter the data model back down under 1 GB.
Secondly, optimize your data model following the guide in this blog in Power BI Desktop, the blog also applies to Power BI Desktop though it is about PowerPivot.
And specify appropriate value in “Command timeout in minutes (optional)" following steps below, then check if you can refresh successfully in Power BI Desktop.
1. Click on the arrow for "Edit Queries" in your current Power BI Desktop file, select "Data Source Settings” in the dropdown.
2. Click on "Change Source..." in the Data source settings pop-up window.
3. Click on Advanced Options in the pop-up window, enter 60 minutes in the "Command timeout in minutes (optional)" textbox, then click OK.
Best Regards,
Community Support Team _ Yalan Wu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi, @Ballabh ;
Query timeout: The reason a command/query runs longer than expected is commonly due to blocking or the need for query/index tuning or bot.
Firstly, based on this blog, in Power BI Service, refreshing the dataset will give an error message letting you know your dataset is too large, and it will fail to refresh until you filter the data model back down under 1 GB.
Secondly, optimize your data model following the guide in this blog in Power BI Desktop, the blog also applies to Power BI Desktop though it is about PowerPivot.
And specify appropriate value in “Command timeout in minutes (optional)" following steps below, then check if you can refresh successfully in Power BI Desktop.
1. Click on the arrow for "Edit Queries" in your current Power BI Desktop file, select "Data Source Settings” in the dropdown.
2. Click on "Change Source..." in the Data source settings pop-up window.
3. Click on Advanced Options in the pop-up window, enter 60 minutes in the "Command timeout in minutes (optional)" textbox, then click OK.
Best Regards,
Community Support Team _ Yalan Wu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
Check out the November 2025 Power BI update to learn about new features.