I’m looking at migrating some of our Percona Server on EC2 instances into Aurora but reading the AWS documentation ( Physical migration from MySQL by using Percona XtraBackup and Amazon S3 - Amazon Aurora ) I noticed this :
- Percona Server for MySQL isn’t supported as a source database, because it can contain
compression_dictionary* tables in the mysql schema.
I’m sure migrating from Percona Server to Aurora is viable, so is this limitation correct or are there ways around it or for those DBs that don’t have those tables is it not an issue? Due to the DB size and other constraints, MySQLdump isn’t really a practical option.
I’ve got to ask… “why”? What’s the reason for moving to Aurora? Having worked with 100s of customers at Percona, Aurora is probably the #1 “buyers remorse” theme I see. Customers move into Aurora, pay 3-5x the cost they were paying before on EC2, then learn that Aurora isn’t doing anything magical for them, and their performance is basically the same as before. I personally have performed several “RDS->EC2” / “RDS->On Prem” migrations this year due to this.
Having done several, yes it is. I have not yet come across this compression_dictionary tables issue before. Perhaps it’s because none of my customers are using that feature?