1 Answer
- Newest
- Most votes
- Most comments
0
Hello wwinogrodzki,
Given that you need to change this setting before upgrading to Aurora 3 with MySQL 8, and considering the limitation of not having an "in-place" upgrade path when modifying this setting, here's a general approach you could consider:
- Create a New Cluster: Set up a new Aurora MySQL 5.7 cluster with lower_case_table_names set to 0 from the start. This ensures the new cluster starts with your desired configuration.
- Export and Import Data: Migrate your data from the existing cluster to the new one. This process typically involves exporting the data (e.g., using mysqldump) and then importing it into the new cluster. Pay special attention to table names to ensure they conform to the new case sensitivity rules.
- Test the Application: Since you mentioned the application works fine with either setting, thoroughly test it against the new cluster to ensure there are no unforeseen issues.
- Upgrade to Aurora 3: Once you've confirmed that the new cluster with lower_case_table_names set to 0 is working correctly, you can proceed with the upgrade to Aurora 3 with MySQL 8. Follow the recommended practices for upgrading, including taking and restoring from snapshots if necessary.
How can I upgrade my Amazon Aurora MySQL DB cluster to a new version? by AWS
answered a month ago
Relevant content
- Accepted Answer
- Accepted Answerasked 7 months ago
- asked 2 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 4 years ago