MAS 500 Migration Troubleshooting.pptVIP

MAS 500 Migration Troubleshooting Darrick Coles Development Manager MAS 500 Agenda Introductions Overview What is Data Migrator? Goals Architecture Key concepts Existing migrations Migration preparation Data tips Performance tips A typical migration MAS 500 Data Migrator Overview Currently supports MAS 90 and MAS 200 versions 3.60, 3.61 and 3.70 MAS 90 and MAS 200cs migrations use ProvideX ODBC driver MAS 200 SQL migrations can be from a DB on the same server or any other server 3.71 support in MAS 500 version 7.0 Supports ad hoc migration and is extensible Part of Assisted Company Setup Multi-step process Extraction Review, clean-up, etc. of the extracted data Insertion into MAS 500 Insertion report available for detailed feedback Assisted Company Setup Enabling an Extraction Goals of Data Migrator Provide competitive advantage when upgrading customers from supported products Provide migrations of critical and/or voluminous data Provide informative feedback Provide a mechanism to fix problems Provide a means for others to plug in their own migration extracts Publish the insertion APIs Allow “in-the-field” extension of Data Migrator Make the delivery of additional migrations easier Enable customers to modify data using existing, well-known tools (Excel) Supported Migration Configurations Key Concepts—Staging Tables Minimal referential integrity (RI) Really, only data type is enforced IDs instead of keys—both foreign and surrogate Most enumerated types replaced by character strings to allow for named values “Yes”, “No” for 0, 1, etc. Flattened, de-normalized structure Other Key Concepts Extraction Copying data from a source system to our staging tables Staging Table Scrubbing Manipulating staging table data—we support: By hand, directly in the staging table Using Microsoft Excel Applying insertion steps before our insertion steps Insertion Applying business rules to staging table data and inserting all records that satisfy the rules Other Key Concepts (cont.)