Question 540
An earlier incident involved this issue: An old billing database uses a locale-specific case-insensitive collation that is not identical on the new engine. Which continuing safeguard would address the risk?
Explanation
Correct Answer
Include collation, encoding and sorting tests in heterogeneous migration acceptance. It targets the actual operating weakness: Migration planning ignores changed string comparison and uniqueness semantics. The immediate repair was: Map source collation requirements to supported target rules and regression-test affected queries.
Incorrect Answers
This would apply data-location controls to temporary transfer resources as well as final instances. It is useful when a finance database is moved to an inexpensive region without considering contracts requiring data to remain in-country, but it does not prevent the issue here: migration planning ignores changed string comparison and uniqueness semantics.
The proposed check would set a clear point of no return based on data flow and rollback feasibility, helping with cases where a company's fallback procedure simply restarts the source after ten hours of new writes on the target. The recurring exposure described here is that migration planning ignores changed string comparison and uniqueness semantics.
This would run source replication-precheck scripts before enabling continuous migrations. It is useful when a Database Migration Service job for MySQL cannot begin CDC even though the source database responds to test SQL queries, but it does not prevent the issue here: migration planning ignores changed string comparison and uniqueness semantics.