Forum Discussion
Data continuity
Hi Petanek333 ,
Firstly, if you have any power over the database structure, you should be getting rid of the year partitions. It's generally poor database structure and causes exactly these types of problems.
Due to the fact that you have partitioned databases your query isn't going to fold however you cut it, so I think your 2022-Disable load/append to 2023 is as good a solution as any. However, I would probably suggest pushing this build process to a Dataflow so PQ isn't trying do it all each time your report refreshes. This also gives you a pre-made source for any future reports.
Pete
Hi Petanek333 ,
Firstly, if you have any power over the database structure, you should be getting rid of the year partitions. It's generally poor database structure and causes exactly these types of problems.
Due to the fact that you have partitioned databases your query isn't going to fold however you cut it, so I think your 2022-Disable load/append to 2023 is as good a solution as any. However, I would probably suggest pushing this build process to a Dataflow so PQ isn't trying do it all each time your report refreshes. This also gives you a pre-made source for any future reports.
Pete
Thank you BA_Pete , unfortunately I don't have any power over the database. I am not familiar with dataflow yet, so a great tip for what to learn.
