Since last year, we've been proactively working on migrating all client accounts to database subdivisions. Essentially, this means we’re moving client data from a single large database into a number of smaller databases in order to provide a better user experience for everyone in the growing aXcelerate community.
Over half of our client base have already been migrated, and have been able to experience immediate improvements in reporting services. This includes faster overnight warehouse reporting, allowing reports to be available until late at night and then ready to use for early morning workflows.
Previously, we have only migrated clients who have opted into the migration by completing the checklist in the aXcelerate System Settings to confirm they are ready.
From 18th March, we will be migrating clients whether they have confirmed or not. aXcelerate has communicated the requirement to prepare for this for over one year and must now migrate all clients, ready or not. Please take a few minutes today to get ready for your migration by actioning the instructions below.
Over the next couple of months, we’ll let your organisation’s aXcelerate Key Contact know via email when your account is due to be migrated, and what you need to do before your migration.
There are a few important steps you need to take before your account migration. Although we will send you a reminder closer to your migration date to complete these steps, we recommend completing them as soon as possible to minimise disruptions to your staff and students.
The steps below should take no longer than 10 minutes to complete.
1. Identify any URLs with your old aXcelerate login domain, and update these to your new subdomain (yoursubdomain.app.axcelerate.com). Make sure you do this for all:
2. Confirm you have completed step 1, or do not need to complete step 1, in your aXcelerate System Settings.
System Settings > Review Checklist
More information about why we are doing this
The biggest disadvantage of using a single database to hold all client data is ‘the noisy neighbour’ effect.
This occurs when an account in the system executes an operation that requires a lot of server power, such as a large AVETMISS report. This can impact other system users, slowing their accounts.
The best solution to this problem is to evenly separate client data into a number of database subdivisions that will provide a much more reliable and scalable user experience. Once client data is separated in this way, there will be more room to grow. This process is also referred to as 'sharding'.
Other benefits include:
To learn more about migrating to a subdomain and its associated benefits, view our Help Guide here.
Product updates and team news delivered straight to your inbox