Data Migration Service

Author: Michael Dombaugh
Version: 1.0
Last Updated: 2026-03-11
Status: Initial Requirements for Review

Requirements

1. PROCESSING: Support batch data movement between any two databases across two supported platforms (SQL Server / Oracle).

2. INPUTS:

• COUNTRY (configurable WHERE clause filter for this use case)
• VERSION (configurable WHERE clause filter for this use case)
• SOURCE DB
• TABLES: discrete list or ALL
• TARGET DB
• TARGET SCHEMA

3. TRIGGER: Initiated by CDR upon successful product build.
(Approval process TBD - Dashboard Control Required)

4. PROCESS STEPS:

• Define a sequential set of steps to be executed during migration
• Steps are configurable and manageable via the dashboard
• Support insertion of stored procedure calls at any step position on either the source or target side
• Steps can be added, removed, and reordered at runtime

5. LOCKING AVOIDANCE: POC to evaluate partition swapping or import table swap mechanism to avoid table locking during batch insert.

6. NETWORK CONNECTIVITY: Cerner network or VPN required to access MIT databases.

7. RECOVERY: Track which tables were successfully moved; on failure, resume with only the remaining incomplete tables. Support restart of a migration that processes only the failed tables in a batch.

8. VALIDATION: Upon completion of data movement, perform record count comparison between source and target for each table moved, by COUNTRY and VERSION. Report any discrepancies.

9. DASHBOARD: Provide visibility and control over sequential process steps, trigger management, migration status, and the ability to define new migration processes.

10. CURRENT USE CASE:

1. Move a defined set of countries from MIT Global_Distribute to OCI GLOBAL_DISTRIBUTE.
2. Call an archive stored procedure to remove the oldest data version after migration is complete (or implement via partition swap - TBD based on POC).
3. Mark the migration as complete in a tracking table in OCI GLOBAL_DISTRIBUTE.

11. ALTERNATE USE CASE:

1. Temporary update from Gen1 Global_Research to Gen1 GLOBAL_PHARMACY, while implementing real-time replication for this.