Question 620
A database team wants to prevent a recurrence of this issue: SQL Server monetary columns arrive as imprecise floating-point values in a PostgreSQL target and totals no longer reconcile. Which preventive practice is most relevant?
Explanation
Correct Answer
Test numerical precision and rounding rules when converting engine-specific types. The original failure arose from: The conversion mapping replaced exact decimal types with approximate numeric representation. The control reduces that failure mode.
Incorrect Answers
For the situation in which a reporting database migration shifts date-only values by one day for some users, it makes sense to test date-only versus timestamp semantics through every cross-engine conversion. Here, the conversion mapping replaced exact decimal types with approximate numeric representation, so the safeguard misses the recurring fault.
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 the conversion mapping replaced exact decimal types with approximate numeric representation.
The failure in the question arises because the conversion mapping replaced exact decimal types with approximate numeric representation. A safeguard to include multilingual sample records in migration data fidelity tests serves situations where a CRM migration converts customers' non-Latin names to replacement characters in the target rather than this one.