Forum Discussion
Date Refresh Timeout issue
Do you get any error messages?
Yeah. The error messages as follows. Do I need change to enterprise gateway?
The refresh operation failed because it took more than 120 minutes to complete. Consider reducing the size of your dataset or breaking it up into smaller datasets.
Cluster URI: DF-MSIT-SCUS-redirect.analysis.windows.net Activity ID: 7678fe84-3b02-49c3-9ff1-67963b1e6359 Request ID: 8e3975fc-f3f9-a4ee-1804-19ca5449ca84 Time: 2016-07-15 04:47:30 This sounds more like an issue with your dataset than the gateway.
Where is the gateway software installed? Are both the SQL database and personal gateway on your own machine?
If so, then Personal Gateway should be fine.
If you have a SQL server and multiple people are viewing the reports in Power BI, then Enterprise is more suited.
How many tables are in your data set?
How many rows are in your largest table?
How many columns are in your largest table?
It might be that you need to do some optimisation first, either by entering a SQL query to only bring in required data, or to create an optimsed data warehouse.
I've worked with quite large databases with a number of years of data that take maybe 40 minutes to refresh, so 120 minutes I think is unusual.
Regards,
Ian
The SQL Server is not in my machine but in the redmond machine and of course multiple people are viewing the reports in Power BI.
So I need use Enterprise right? How to use Enterprise to connect?
We have 50 tables. The largest have 6563357 rows and 30 columns.
We do some filter in Advance Editor, is it will impact the speed?
