AWS dms documentation change
Summary
Generalized collation difference handling description to all source/target databases
Security assessment
Clarifies validation behavior but does not address security aspects.
Diff
diff --git a/dms/latest/userguide/CHAP_Tasks.CustomizingTasks.TaskSettings.DataValidation.md b/dms/latest/userguide/CHAP_Tasks.CustomizingTasks.TaskSettings.DataValidation.md index 73745ba68..88b385ffc 100644 --- a//dms/latest/userguide/CHAP_Tasks.CustomizingTasks.TaskSettings.DataValidation.md +++ b//dms/latest/userguide/CHAP_Tasks.CustomizingTasks.TaskSettings.DataValidation.md @@ -17 +17 @@ The data validation settings and their values include the following: - * `HandleCollationDiff` – When this option is set to `true`, the validation accounts for column collation differences in PostgreSQL and Microsoft SQL Server endpoints when identifying source and target records to compare. Otherwise, any such differences in column collation are ignored for validation. Column collations can dictate the order of rows, which is important for data validation. Setting `HandleCollationDiff` to true resolves those collation differences automatically and prevents false positives in data validation. The default value is `false`. + * `HandleCollationDiff` – When this option is set to `true`, the validation accounts for column collation differences between source and target databases. Otherwise, any such differences in column collation are ignored for validation. Column collations can dictate the order of rows, which is important for data validation. Setting `HandleCollationDiff` to true resolves those collation differences automatically and prevents false positives in data validation. The default value is `false`.