MyTimetable database migration - calendar integrations

We will be performing maintenance work on the MyTimetable hosting platform in the week of the 30th of October.

What will be done?

During this maintenance window we will migrate the following MyTimetable databases from our legacy to our new database infrastructure:

MyTimetable External Calendar Integration database (for the Office 365 / Google Calendar native integration)

When will MyTimetable be unavailable?

Your MyTimetable calendar integration might be unavailable for around 15 minutes at some point during the week. The unavailability is required to make sure that no changes are made to the database during the migration. MyTimetable itself will remain fully available, except for the functionality to manage the calendar integration.

Please note that many customers are already on the new database infrastructure, and will therefore not experience any interruption of the service at all. It is also possible you are not using this optional module. In that case, you will also not experience any interruption of the service.

Why is this necessary?

At the moment, MyTimetable is using two database infrastructures. We have decided to consolidate these into one infrastructure.

This improves the availability and resilience of our platform and allows us to offer point-in-time recovery for the abovementioned databases. Furthermore, the MyTimetable software only needs to support one infrastructure, allowing us to simplify the software and decrease the risk of database specific bugs.

Are there any risks involved?

The risk involved is considered low. Many customers are already using our new database infrastructure for years and we have included several checks in the migration process to make sure all data is copied over. When migrating the acceptance environments, no issues have occurred.

What will happen if the database migration fails?

If the migration fails or if the calendar integration is not working as expected, the change will be rolled back.