Hello,
We have a requirement to build a cube that will have roughly 100k rows to start (necessary to account for every combination of day and dimension in a year). After activation it will update on insert and removal. Any considerations with a data set this size? Should i activate on off business hours? Or should the system be able to handle this load. This table will grow over time and has the potential to hold up to 5 years of data.
Thanks!
Activation doesn’t need to happen outside of business hours, and the Summary Table framework should be able to manage the activation process just fine and not impact other systems. That dataset sounds quite manageable to me. I don’t have any recommended considerations beyond make sure you’re familiar with the relevant sections in Nextworld Help, especially the topic on Summay table best practices.
I need to revise my above comments. If a summary table is loaded during business hours, it will likely create a high async-task-service ATS backlog. This will result in the ATS service being throttled in the subject environment. When the ATS service gets throttled, this impacts automatic workflow transitions which, along with summary table events, go through the ATS process. Automatic workflow transitions may be delayed for a short period of time as the ATS rejects work per the applicable throttling parameters.
