Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
Hi,
I am trying to implement Incremental refresh and not having much success with .. a couple of questions
Many thanks
Solved! Go to Solution.
1. datetime or dateinteger
2. convert/cast to datetime
3. don't use that unless absolutely necessary
4. store 5 years, refresh 24 months
5. no. If you specify months then the smallest partition will be month
6. only if you sit on your hands. Older partitions will be recreated when you make meta data changes and republish the pbix, and you can also manually update those partitions.
Thanks for quick reply...
what the best method to convert our datetimezone col to dattime?
what would the reason be not to use detect changes ?
how does the partition refresh work if detect change isnt used
so if we have a window of 24 mths .. any changes within the 24 mths will get picked up.. is that correct?
thanks
1. DateTime.From()
2. it doubles the dataset size
3. refresh will be done based on the refresh rules you specified (ie the top 24 partitions)
4. yes
hi,
re #3 ... presume it will only refresh the partitions it needs to within the 24 mths ... is that correct ? We have lots of data in our 24mth window and would not want whole 24mth to get pulled in every time.
Thanks
if you specify 24 months then it will refresh all 24 partitions. If you don't want that, specify a smaller window and refresh the older partitions on a manual basis (every quarter for example). If you really must, read about the "Detect Data Changes" process again, identify a suitable column, and try it out. (Not endorsing that, but your situation might require it)
1. datetime or dateinteger
2. convert/cast to datetime
3. don't use that unless absolutely necessary
4. store 5 years, refresh 24 months
5. no. If you specify months then the smallest partition will be month
6. only if you sit on your hands. Older partitions will be recreated when you make meta data changes and republish the pbix, and you can also manually update those partitions.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.