Refresh Dataset in 2 batches to avoid two hour time-out

[Anonymous]

Hello,

I'm facing an issue when I cannot complete a refresh due to two hour refresh limit. My datasource is Teradata and I'm loading 10 different tables. 

My main question is:

1. Is it possible to divide refresh in PBI Service into 2 batches (5 tables + 5 tables) to avoid the time out issue?

I also would appraciate if anyone could help with below.

2. Is it worth to change .NET Driver for ODBC for better performance for TERADATA? 

3. Is the below error message the one that returns PBI due to two hour timeout?

Many Thanks in advance, Kamil

[wikkleyn]

Hi @Anonymous 

1. If you are using Premium, you can split the refresh by using a dataflow. 

2. We have tried both and found the .NET Driver for ODBC didn't perform better. I have found that odbc sources add additional maintenance on the gateway. 

3. The timeout is on Teradata. You can overwrite that in the advance settings of your query. Also, check with the Teradata dba if they aren't throttling your user. 

[Anonymous]

Hello @wikkleyn and thanks for help.

Just to be more specific regarding point 2 - are you trying to say that ODBC will be faster? What do you mean by additional maintanance on the gateway? 

Thanks! Kamil

[ibarrau]

Hi, let's see

1- The only way to refresh specific items would be with dedicated capacity and the enhanced refresh API. If you have shared capacity (pro license) then no.

2- I really don't know the answer for this one.

3- That's not the PowerBi two hours timeout. The error says that it was aborted by a user. There might be a timeout over teradata to cancel querys if they take too long. If power query let you write a query for teradata it also let you configure a timeout for the query (advance settings when connecting). Even though if the query takes 2 hours you can't increase that timeline and make it work.

You can look for reducing or downsizing data model in order to help with the time range of the refresh.

I hope that helps.