CUBRID Lowers Oracle Win-back Barriers with Launch of Migration Analysis Tool 'CMA'
IT DAILY ·
✦ AI Summary
CUBRID said on the 4th that it has launched an analysis tool, 'CUBRID Migration Analyzer (CMA·CUBRID Migration Analyzer),' to help companies review in advance when switching Oracle DB to its own DBMS.
CMA focuses less on direct data migration than on identifying DB objects and application queries that need modification during migration, as well as estimating the expected workload.
The analysis results include success and failure status, compatibility ratio, failure reasons, related SQL, and estimated modification workload, and CMA is a tool used by CUBRID's internal technical support staff.
CUBRID said on the 4th that it has launched an analysis tool that companies can review in advance when considering switching Oracle DB to its own DBMS. The tool is called 'CUBRID Migration Analyzer (CMA·CUBRID Migration Analyzer).' Its purpose is to conduct a preliminary analysis of switching Oracle DB to CUBRID.
CMA focuses less on direct data migration and more on identifying the DB objects that need to be modified during a transition. It also focuses on identifying application queries that need to be modified and estimating the expected workload in advance. Through this, it performs technical difficulty analysis and modification scope analysis before migration.
CMA is not intended for customer sales or external distribution, and is a tool used by CUBRID's internal technical support staff. The tool helps customers determine whether to proceed with migration and establish a specific transfer plan.
The key point of this launch is to reduce the uncertainty involved in migration, which is cited as a barrier to Oracle Win-back entry. When replacing a DBMS, compatibility must be checked for data, existing DB objects such as procedures and functions, and SQL including applications. If this is not examined accurately in advance, unexpected modification work may arise after migration, which can lead to higher costs and longer schedules, making the accuracy of pre-analysis critical to the success or failure of the project.
CMA provides functions to identify the number of Oracle DB objects, determine table sizes, and estimate the number of records. It also analyzes items that need compatibility verification during the CUBRID migration process and items that require modification during the CUBRID migration process.
CMA analyzes DB internal objects and SQL in MyBatis mapper XML files, which are widely used in Java applications. CMA is not limited to checking convertibility at the DB level; it also provides a function to check queries that include real applications, enabling a broad understanding of the scope of migration impact.
The analysis results include success and failure status by item, compatibility ratio, failure reasons, and related SQL, along with an estimate of the modification workload. The estimated workload is calculated by applying weighted factors based on multiple variables, including unsupported functions and query length.
Technical support staff can use this information to determine priorities for items to be modified and to establish project staffing plans and project schedules. However, the estimated workload is a reference value based on CUBRID's calculation criteria, and actual work time may vary depending on the customer's DB environment and the scope of modifications.
The analysis report is provided in HTML and text formats. Through this, users can review the overall analysis results, object-by-object errors, and workload calculations, and it can be used for internal technical review and for establishing transfer plans for customers.
CUBRID said it differentiates the roles of CMA and CUBRID Migration Toolkit (CMT·CUBRID Migration Toolkit). CMA handles pre-migration diagnosis of DB size, pre-migration compatibility diagnosis, and pre-migration modification workload diagnosis, while CMT is responsible for the actual data migration after analysis.
CUBRID operates its Oracle Win-back support process in more granular stages. The support model is divided into pre-diagnosis and planning using CMA, and actual migration based on CMT. This goes beyond simply providing a data transfer tool and establishes a system in which technical support staff can become involved from the early stage of evaluating whether to proceed with migration.
Companies considering a transition from a commercial DBMS to an open-source DBMS must take into account not only license cost savings but also compatibility with existing systems and application modification costs. In this respect, CMA is tasked with quantifying modification scope and workload that are difficult to identify in advance. It is presented as playing a role in supporting initial review and migration preparation.
CUBRID CEO Jung Byung-joo said the core of Oracle Win-back lies in helping customers understand the scope of migration and required work in advance and supporting transfer preparation. He also explained that the company plans to use CMA to enhance the pre-analysis capabilities of technical support staff and strengthen support for CUBRID migration tailored to customer environments. The use of CMA is expected to serve as a technical support measure for CUBRID's efforts to capture demand for Oracle alternatives.
Source: IT DAILY · By Lee Jae-young
Original: https://www.itdaily.kr/news/articleView.html?idxno=241402
References
This article was produced with the help of an automated content generation algorithm.
Source: IT DAILY
View originalThis article was summarized and organized by BizCrush based on the original article from IT DAILY. For exact quotations and full details, please refer to the original article.