Data migration process for an application whose architecture is changing?

After using the application for more than 10 years and constantly limited by the lack of extensibility, we decided to completely rewrite it from scratch. Since the new architecture is different from the old application, the database is also different. Here the problem arises: Is there any industrial process for transferring data from a previous database to a new one? Some tables are similar, while others are not. In general, we need a process that will help us make sure that no data or logical limitations are lost during the migration.

PS: The old and new database are Oracle databases.

+3
source share
2 answers

Although you do not indicate this in your question, I assume that you are going to develop a new version of your application / database, and then at some switching point you need to transfer all current data from the old database to your new database.

If so, then you are really asking about two different processes: the migration (with some changes) of the database structure, and then the subsequent migration of the data itself.

, ( , "" - , ). ; . , , , .

, -tested . - . ( ), , . , , , "" .

+6

. , , Microsoft Access ODBC- Oracle. Access .

Microsoft SQL Server. Business Intelligence Development Studio SSIS Oracle. SSIS , , SQL Server, .

SSIS:

http://www.developerdotstar.com/community/node/364

Oracle Warehouse Builder (OWB). , Oracle ETL (Extract, Transform Load). , , .

+2

Source: https://habr.com/ru/post/1718027/


All Articles