Question 640
A postincident review documents: A mapping application drops geometries when moving spatial columns between SQL engines. Which ongoing check targets the underlying failure?
Explanation
Correct Answer
Check spatial type and coordinate-system compatibility before migration. The recurring risk is source spatial types and coordinate reference systems lack compatible target mappings. This check makes that risk visible before another incident.
Incorrect Answers
The proposed safeguard is useful where a database migration moves tables but dozens of stored procedures continue using source-engine functions. It would not address recurrence of the underlying issue here: source spatial types and coordinate reference systems lack compatible target mappings.
This control would estimate target logical data, indexes and temporary build space in migration plans; it responds to the risk in which a managed destination database is provisioned with less storage than the source's live tables and planned index overhead. It would not address the current root cause: source spatial types and coordinate reference systems lack compatible target mappings.
This control would execute batch-job compatibility suites before changing database engines; it responds to the risk in which a T-SQL job from SQL Server fails on PostgreSQL because it uses engine-specific temporary table and variable syntax. It would not address the current root cause: source spatial types and coordinate reference systems lack compatible target mappings.