Forum Discussion

robarivas's avatar
robarivas
Post Patron
6 years ago

Initial Incremental Refresh Fail

Set up my first Incremental Refresh. It ran for 8 hours on the Service and then failed with the following error message:   {"error":{"code":"DM_GWPipeline_Gateway_TimeoutError","pbi.error":{"code":...
Need Help
robarivas's avatar
robarivas
Post Patron
6 years ago

Thanks again v-kelly-msft for your response. However, that link has to do with disabling Query Folding, which I'm sure must be the opposite of what I would want. My problem, I suspect, might be that Query Folding isn't happening whereas it ought to be. Or maybe something else entirely is going on here. I don't know. Hopefully the Community and/or Microsoft employees can assist.

 

GilbertQ I do not have familiarity (nor access I believe) to run SQL Profiler. The entire data set (180+ million rows) takes roughly 6 hours to load in to the Power BI data model on the desktop. I do not believe indexing has been set up on the SQL Server table (yet).

 

I'd just really like to know why I receive the Incremental Refresh Query Folding warning. None of the possible reasons for why that warning should/would show up appear to exist in this case. I suspect that warning might help explain and/or have something to do with the exceedingly slow initial refresh problem that originally motivated this thread.

 

I do know that steps after the Incremental Refresh parameter filter break query folding but my understanding was that as long you've got query folding maintained up through the step where the RangeStart and RangeEnd filters are applied you should be good to go. Might that not be the case?

  • v-kelly-msft's avatar
    v-kelly-msft
    Community Support
    6 years ago

    Hi  robarivas ,

     

    I cant reproduce your scenario,so better create a support ticket via below link:

    https://powerbi.microsoft.com/en-us/support/

     

    Here  is the reference about how to create the support ticket.

     

    Best Regards,
    Kelly
    Did I answer your question? Mark my post as a solution!

     

    • Anonymous's avatar
      Anonymous
      Not applicable
      6 years ago

      robarivas Did you find a solution for this? I'm facing the same issue

      • robarivas's avatar
        robarivas
        Post Patron
        6 years ago

        Hello Anonymous I am still working with Microsoft on a ticket for this. However, I tried changing the (SQL) server name in the M query on the dektop file (pbix) from uppercase to lowercase to match how I have that SQL server connection setup on the gateway and I also, for now, removed joins/merges to some dataflows. One of these changes seems to have allowed the report to successfully execute incremental refresh. Either one is ridiculous in my opinion. If/when I can confirm which (if either) was the resolution I'll post another response.