Xoriant Database Migration Case Study

Table of Content

1. Client Overview

2. Business Situation

3. Challenges

4. Our Solution - Methodology & General Milestones and     Deliverables

CLIENT OVERVIEW

Our client is a high growth telecommunications software vendor with worldwide operations in the high flux telecom market. Our client's products allow mobile network operators to rapidly deploy a flexible, open, next-generation wireless network to offer their customers rich voice, data and multi-media services. Additionally, the company provides a series of actionable alerting solutions to financial institutions to assist them in increasing revenue, lowering operating costs and improving customer satisfaction and retention.

Top

BUSINESS SITUATION

Corporate databases in recent years have mushroomed both in size and in costs to maintain. As companies continually become more sensitized to the cost of their existing technology infrastructure, databases are increasingly seen as strong potential targets for financial savings due to significant growth in licensing and yearly maintenance expenses as CPU power and/or user strength increases. Our client’s major portion of IT budget was being consumed by their existing infrastructure and too little was available for new IT initiatives. Our client wanted to opt for databases as an ideal starting point to exercise this new IT infrastructure philosophy by certifying their leading business products on open source database technology (Oracle Database 9.2.0.x to MySQL 5.0.x)

Top

CHALLENGES

Moving a huge database of the size of approximately 210 GB while simultaneously optimizing the performance of the migrated database involved number of challenges, some of which were:

• Determining the optimal infrastructure configuration to enable smooth migration was one of the bigger challenges

• Ensuring minimal downtime during the migration since the database to be migrated was OLTP with high throughput, many users, and constant load of DML operations and queries

• Ensuring high usability and manageability offered by the Oracle database

• MySQL does not support numerous features like scheduled jobs, several Oracle data types, sequences and schemas like XMLDB

Top

OUR SOLUTION - METHODOLOGY & GENERAL MILESTONES AND DELIVERABLES

• We conducted an in-depth infrastructure analysis of number of database users, type of database workload, etc to determine number and type of servers and CPUs needed and utilization rate of each server

• We used InnoDB storage engine of MySQL that is a transaction-safe, ACID (atomicity, consistency, isolation, durability) compliant and best suited for OLTP

• MySQL Migration toolkit was used for migrating simple tables and views and the data

• Open source tool SqlYog was employed that provides rich and efficient usability experience

• We created a set of stored procedures, shell scripts and Cronjobs to replace the Oracle jobs

• A proprietary tool was developed to simulate heavy traffic condition for performance testing

• Shell scripts were written to load the data in bulk (approx 3.5 million rows) and benchmarking was done with the original database to determine the performance in terms of time taken for transaction processing

• Generated application reports for data verification

To ensure smooth and error free migration, we followed required steps from a detailed methodology for the migration framework defined by Xoriant Open Source COE as illustrated:

Top