Forum Discussion
Could a Derived DateTime Partition Column Affect Incremental Refresh Performance?
Hi manoj_0911 ,
Can you check the amount of data you are processing in the refresh ?The issue could be because of the volume of data being processed during the initial refresh.
A good first step would be to reduce the amount of data being loaded and test the refresh behavior.
What I usually do is create a parameter called LoadData (True/False) and use it in the Power Query layer as shown below:
Letsource....#"FirstNRows" = Table.FirstN(Source, 10),#"DataLoad" = if Loaddata then Source else #"FirstNRows"in#"DataLoad"
In Power BI Desktop, keep the parameter set to False by default to avoid encountering this issue during development.
Publish the file with parameter = False and do the first refresh so the partitions are created .Once the partitions are created, set the parameter to True in the Power BI Service and refresh each partition using SSMS.
If this response was helpful, please consider giving it a kudo and marking it as the correct solution—it helps other community members find answers more quickly.
Hi manoj_0911 ,
Can you check the amount of data you are processing in the refresh ?
The issue could be because of the volume of data being processed during the initial refresh.
A good first step would be to reduce the amount of data being loaded and test the refresh behavior.
What I usually do is create a parameter called LoadData (True/False) and use it in the Power Query layer as shown below:
In Power BI Desktop, keep the parameter set to False by default to avoid encountering this issue during development.
Publish the file with parameter = False and do the first refresh so the partitions are created .
Once the partitions are created, set the parameter to True in the Power BI Service and refresh each partition using SSMS.
If this response was helpful, please consider giving it a kudo and marking it as the correct solution—it helps other community members find answers more quickly.