We have kept all of our CALE events in a single object, but I'm considering breaking it apart so that updating it won't take so long. When we click "save" it requires several minutes to generate its table, and automated tasks that should be triggered in that timeframe will fail to launch with unable-to-access-cale errors.
So I'm fishing for recommendations of how to break our large CALE apart into smaller ones? Should I try putting all weekly events into one CALE, all monthly events into another CALE, for example? How do you do it?
I have also observed that it is the jobs that run many times a day that are at the most risk. And of course it would be great if the product were more resilient than it is when the calendar is being updated.
I'm coming to the conclusion however that splitting our calendar would not offer 100% protection, and therefore might offer a false sense of security to our staff. It might be just as well that they continue to have to schedule calendar updates for a quiet time on the weekend.
I might do some experiments though with moving just the most static kinds of events into their own calendar, such as MON/TUE/WED and JAN/FEB/MAR. It feels like unnecessary overhead to have to re-generate these sorts of events every time we want to update our calendar.