Oracle to DB2 Migration Metrics

Transcription

1 Oracle to DB2 Migration Metrics Catalyzing Growth September 2001

2 Table of Contents 1. Metrics for a typical Oracle to DB2 Migration project: Engagement Tasks and Project Experience Delivery Assurance and USP Partnerships Office Locations and Contact Address... 9 Migration Metrics Page: 2 of 9 Ver.1.0/Dt: 8/28/01

3 1. Metrics for a typical Oracle to DB2 Migration project: A Typical RDBMS platform is made up of various Components as listed in the following table. These are treated both individually and severally while effecting a migration to another RDBMS platform. Each component transformation would need an initial Preparation phase followed by the Conversion phase. The Man-days requirement for both these phases, Component wise, is shown below (with a caveat that these figures are only indicative, based on our past experience and may have a 10% variation in future projects). Preparation is the planning phase for analyzing the Component and Designing a transformation solution. The Man-days shown under this may remain the same for different number of units of the corresponding Component. Conversion is the execution phase for realizing the transformation of an element. The Man-days shown in this phase varies in direct proportion to the number of units of the corresponding Component. The last component, General, covers project issues outside the technical ambit of Migration. This is more in actual days rather than man-days. Migration Metrics Page: 3 of 9 Ver.1.0/Dt: 8/28/01

4 (Man-days) Components Preparation Conversion Total DDL Server Side Codes Table Index View Stored Procs Triggers Functions Batch Jobs Tasks Data Volume 4 GB Application UI Screens Business Logic 20 kloc Reports Total Man-days General Pre-Sales 15.0 DBA-related 20.0 Transfer of Solution Tables Any typical database migration would take up DDL conversion as the first step and Table is the main component of DDL to be converted first. The main elements of Table are Columns, its Data types, Keys and Constraints. 2. Index is used to improve performance and speed up accessing required data in tables. It is typically a mini-table consisting of relevant columns from tables, like Primary keys, foreign keys, and Non-key columns. This is generally handled by the DBA. 3. Views are Tables without any data content outside of a running application context. The main components of views are the Select statements on base table/s with related clauses. Migration Metrics Page: 4 of 9 Ver.1.0/Dt: 8/28/01

5 4. Stored Procedures provide for server side implementation of business logic. Issues with SP migration are LOC of PL/SQL, # of SQLs, #Begin-End modules, Calls to other SPs and function Calls, these will be renovated using our PL./SQL Renovator tool. 5. Trigger is a powerful mechanism to build an automatic process of ensuring Database integrity. Issues involved in converting triggers are LOC of PL/SQL, Trigger event, # of SQLs, and Calls (if any) to SPs, these will be renovated using our PL./SQL Renovator tool. 6. Functions in RDBMS have the standard utility of computing and returning values. The main issues involved in migrating the Functions are LOC of PL/SQL, data type and value being returned, # of SQLs, and Calls to SPs (if any), these will be renovated using our PL./SQL Renovator tool. 7. Batch job tasks: This is a significant component of most Legacy applications. Involves # Transaction files and # Batch runs. 8. Data: This item actually refers to another phase in RDBMS migration. It addresses the actual transfer of gigabytes of data. The Preparation phase evolves a strategy for data transfer, like Hash total checking, creation of small programs to effect the transfer. The execution phase involves the total data transfer, verification, and reruns. This phase heavily depends on number of tables, and Records. 9. User Interface: Application migration involves User interface conversion, Business Logic Conversion and Report generation (if required). Conversion of User Interface screens depends on #Screens, Components (text box, objects, text area, etc.,) and related validations. 10. Business Logic: Involves analysis and conversion of functions, subroutines and external routines and also depends on LOC of the procedural language used. 11. Reports: Migration of reports depends on # Reports, Customization of Reports and Dynamic report generation. We recommend use of popular Report generators, like Business Objects, Crystal Reports, etc. Migration Metrics Page: 5 of 9 Ver.1.0/Dt: 8/28/01

6 2. Engagement Tasks and Project Experience Engagement Tasks Application Analysis Renovation Maintenance SDLC Engagement Level Scope Study Pilot Fixed price Project Time and Material project Intertec Project Experience Technology Base NO. Of Projects Legacy Systems 15+ Open System 20+ Microsoft Technology 20+ CRM 10+ Embedded System/ Wireless 20+ Project Experience by Services Type Maintenance & Enhancements 25+ Re-engineering Renovation 25+ Web Enabling 25+ Software Development Life Cycle 35+ Migration Metrics Page: 6 of 9 Ver.1.0/Dt: 8/28/01

7 3. Delivery Assurance and USP Delivery Assurance is a key factor in the overall client engagement within Intertec. Each project is run by a seasoned Project Manager, who ensures that all aspects of your solution is delivered on time, to budget with the highest possible quality. We use several proven techniques to ensure delivery. Mass Customization An approach to chart an optimum path between building a solution from scratch and buying off-the-shelf products Delivery Organisation Structure QMS Knowledge Management ISO-9001 certified, en route to SEI CMM Level-5 A ctivating the engagement L everaging existing knowledge and tools E laborating and building on it R realization of the clients objectives T transition to the clients environment Account Manager Business Unit Head Project Manager Business Analyst Project Lead Project Team Members Project QA/Testing Team Unique Selling Preposition Short Delivery Cycle Focused Business Structured Team Multiple Engagement Options Investment in creating IP Experience Functional expertise Local Partnerships Enabling Tools Technology Partnerships Migration Metrics Page: 7 of 9 Ver.1.0/Dt: 8/28/01

8 4. Partnerships Our technology partnerships with world leaders such as IBM, Microsoft, Sun, Remedy and BEA Systems add to our capability. To ease client reach and better understand the specifics of a particular domain, Intertec has forged business partnerships with AdPac Corporation, Venture Portfolio Inc., AR Focus Inc. in USA, Systems Management International, FactDelta Ltd. in UK, and KoCos in Germany. * All trademark and logos are the properties of the respective organisations. Technology Partners Business Partners Migration Metrics Page: 8 of 9 Ver.1.0/Dt: 8/28/01

9 5. Office Locations and Contact Address United States of America 1. Intertec America Inc. 425, Market Street Suite-400, San Francisco, CA Intertec America Inc. 6580, Jimmy Carter Blvd. Norcross, GA United Kingdom Intertec Software Solutions Ltd. Alexandra House Alexandra Road Swansea Road SA1 5ED Phone / Fax: mailbox@intertec1.com INDIA Intertec Communications Ltd. #28, Shankar Mutt Road, Bangalore , India. Ph: /1317 Fax: info@intertec1.com Migration Metrics Page: 9 of 9 Ver.1.0/Dt: 8/28/01