sql-serveroracle-databasedata-migrationscriptella

How to handle data migration integrity issues?


I am dealing with a data migration from an old SQL Server 8 database to an Oracle 11g. I am talking about 100 tables more or less and tons of data. I am using Scriptella ETL. The problem is, there have been changes in foreign keys, there are new constraints for the new database, so there are integrity errors when enabling constraints after executing the migration. I have executed it in two different development environments and the errors are different, so I had to solve it manually. With such amount of data is impossible to predict where those errors are going to appear in testing and production environment. What is the best way to handle this issue?

Thanks!

Edited 10/28/2016:

I found Oracle has this option "ENABLE NOVALIDATE" so I tried it and it works! But now my question is, there is negative consequences to have data without integrity in DB?


Solution

  • I finally solved it by using the Oracle option "ENABLE NOVALIDATE" though I don't know if it has negative side effects.