FlexiDC:A Flexible Platform for Database Conversion

1979

Abstract As requirements change, database administrators come under pressure to change the schema which is a description of the database structure. Although writing a new schema is a relatively easy job and transforming the database to match the schema can be accomplished with a modest effort, transforming the numerous programs which operate on the database often requires enormous effort.

2016

The Database Preservation Toolkit is a software that automates the migration of a relational database to the second version of the Software Independent Archiving of Relational Databases format. This flexible tool supports the currently most popular Relational Database Management Systems and can also convert a preserved database back to a Database Management System, allowing for some specific usage scenarios in an archival context. The conversion of databases between different formats, whilst retaining the databases’ significant properties, poses a number of interesting implementation issues, which are described along with their current solutions. To complement the conversion software, the Database Visualization Toolkit is introduced as a software that allows access to preserved databases, enabling a consumer to quickly search and explore a database without knowing any query language. The viewer is capable of handling big databases and promptly present search and filter results on mi...

Lecture Notes in Computer Science, 2008

This paper presents an investigation into approaches and techniques used for database conversion. Constructing object views on top of a Relational DataBase (RDB), simple database integration and database migration are among these approaches. We present a categorisation of selected works proposed in the literature and translation techniques used for the problem of database conversion, concentrating on migrating an RDB as source into object-based and XML databases as targets. Database migration from the source into each of the targets is discussed in detail including semantic enrichment, schema translation and data conversion. Based on a detailed analysis of the existing literature, we conclude that an existing RDB can be migrated into object-based/XML databases according to available database standards. We propose an integrated method for migrating an RDB into object-based/XML databases using an intermediate Canonical Data Model (CDM), which enriches the source database's semantics and captures characteristics of the target databases. A prototype has been implemented, which successfully translates CDM into object-oriented (ODMG 3.0 ODL), object-relational (Oracle 10g) and XML schemas.

2008

Relational DataBases (RDBs) are dominant in the market place yet they have limitations in the support of complex structure and user-de ned data types provided by relatively recent database technologies (i.e., object-based and XML databases). Such a mismatch inspires work on migrating an RDB into these technologies. The problem is how to effectively migrate existing RDBs, as a source, into the recent database technologies, as targets, and what is the best way to enrich RDBs' semantics and constraints in order to meet the characteristics of these targets? Existing work does not appear to provide a solution for more than one target database. We tackle this question by proposing a solution for migrating an RDB into these targets based on available standards. The solution takes an existing RDB as input, enriches its metadata representation with as much semantics as possible, and constructs an enhanced Relational Schema Representation (RSR). Based on the RSR, a canonical data model is generated, which captures essential characteristics of the target data models that are suitable for migration. A prototype has been implemented, which successfully migrates RDBs into object-oriented, object-relational and XML databases using the canonical data model.

International Journal for Research in Applied Science & Engineering Technology (IJRASET), 2022

The data migration process is usually needed when there is a change in system, format, or storage type. Currently, there are several techniques and tools for migrating data, for example, CSV files, ODBC, SQL Dump, and so on. Inappropriately not all of these techniques can be implemented for migrating data between two different DBMS. This research describes a data migration technique that can be used to migrate data across DBMS. The data migration technique described makes use of existing metadata in each DBMS. The data migration process described here goes through three stages, namely capture, convert and construct. A prototype was built to test this data migration technique. By using the HR schema, cross-DBMS data migration trials were carried out between Oracle and MySQL. Using this technique, full-schema data migration takes an average of 20.43 seconds from Oracle DBMS to MySQL and 12.96 seconds for the reverse scenario. As for partial data migration, it takes an average of 5.95 seconds from Oracle DBMS to MySQL and 2.19 seconds for the reverse scenario

1984

The dominance of traditional relational databases (RDBs) on the market and their inability to support complex structure and user-defined data types provided by object-based/XML databases makes conversion of an existing RDB into object-oriented database (OODB), object-relational database (ORDB) and eXtensible Markup Language (XML) database an active research area. We tackle this problem by proposing an integrated method, called MIGROX, for migrating any existing RDB into OODB/ORDB/XML based on available standards. System architecture has been designed and a prototype implemented to demonstrate the migration process. This report describes in details the evaluation of MIGROX. Two experiments have been setup to examine the differences between a source RDB and each of three target databases resulted from the prototype. The prototype outputs was given and overall results of the evaluation are discussed. The results show that the source and target databases are equivalent, and demonstrate that the MIGROX solution, conceptually and practically, is feasible, efficient and correct.

Proceedings of the 37th annual Southeast regional conference (CD-ROM), 1999

In this paper, we introduce a new approach of database integration, through the use of the Extensible Markup Language (XML). We also demonstrate the applicability, through an experiment with an XML subset we call BSML (Bookstore Markup Language) that integrates heterogeneous bookstore databases. BSML addresses a valid problem associated with network-accessible databases, and demonstrates an XML-based solution to the problem. This approach is quick, affordable, and convenient that does not require a large investment of capital and resources when integrating databases.

2016

the ambition of this study is to discover a technique to assimilate several various databases like MySQL, Oracle, Sybase, Postgre, by taking the help of some of the modern Web technologies. It provides a global interface for these databases, accepts a query from the user in a natural language format (English), decodes this query into SQL using an interpreter, then retrieves data from the database, displays the result to the user and translates it into a fused format. XML is the fused format which helps to assimilate the data. To accomplish assimilation of data, we will implement an interpreter, which will take user query as its input and provides aimed appropriate data as output. The queries will be applied to core database to retrieve information from it and display to the end user. During this process, the retrieved data will be translated into XML format and piled as an XML document. The produced document can be used further for other XML processing like translating it into HTML ...

Users extract knowledge from the database by posing Quires. Most of the users submit SQL Query to extract information from the database. This makes a restriction on users to be familiar with SQL tool. Our proposal is to integrate the existing different database schemas into a single common format. It is widely recognized that integration of database and information retrieval is gaining more importance recently. To enable convenient access to the data organized in different database schemas, we have proposed a new Heterogeneous Data Base Connectivity (HDBC) architecture with graphical user interaction that can be used even by a novice person to create, manipulate and extract information in any database schema. The proposed algorithm also gives provision to export table from one database to another and supports excellent searching capabilities. User friendly interaction is ensured and hence this work enables the end user to retrieve information in an efficient manner from the database organized in different schema and can easily integrate and share the processed information across different applications.

1984

Translation experience among agency personnel is often acquired through " live-and-learn" , on-the-job conversion projects. In-house learning experiences are often very expensive -especially so in this in- stance because database translation can be very com- plex. To describe the data structures of proposed standard DBMS data models. To describe a recommended approach to database trans- lation based upon a standard data interchange format. To present results of database translation studies undertaken by the Institute for Computer Sciences and Technology (ICST) . Chapter 2 describes the database translation process and summarizes the current state of research in this area. Following that, we discuss in chapter 3 the various inter- change forms that have been proposed as potential standards. * the description of data elements, vectors, arrays, and hierarchies containing character strings, bit strings, and numeric forms.

2008

One important problem in today organizations is the existence of non-integrated information systems, inconsistency and lack of suitable correlations between legacy and modern systems. One main solution is to transfer the local databases into a global one. In this regards we need to extract the data structures from the legacy systems and integrate them with the new technology systems. In legacy systems, huge amounts of a data are stored in legacy databases. They require particular attention since they need more efforts to be normalized, reformatted and moved to the modern database environments. Designing the new integrated (global) database architecture and applying the reverse engineering requires data normalization. This paper proposes the use of database reverse engineering in order to integrate legacy and modern databases in organizations. The suggested approach consists of methods and techniques for generating data transformation rules needed for the data structure normalization.

2013

Database integration is a multistep process of finding similar entities in two or more databases to create a non-redundant, unified view of all databases. Database integration has become an active area for research due to increasing of information resources with the need of users and applications to integrate data from these different sources. This paper discusses the role of data integration and the fields that require it, problem of integration and the processes of integration. Finally it presents the current methods used in database integration in a form of graph that classified the approaches in clear manner.

Applied Sciences

In a world rich in interconnected and complex data, the non-relational database paradigm can better handle large volumes of data at high speed with a scale-out architecture, which are two essential requirements for large industries and world-class applications. This article presents AMANDA, a flexible middleware for automatic migration between relational and non-relational databases based on a user-defined schema that offers support for multiple sources and target databases. We evaluate the performance of AMANDA by assessing the migration speed, query execution, query performance, and migration correctness, from two Relational Database Management Systems (RBMSs), i.e., Postgres and MySQL, to a non-relational database (NoSQL), i.e., DGpraph. The results show that AMANDA successfully migrates data 26 times faster than previous approaches, when considering Northwind. Regarding the IMDB database, it took 7 days to migrate 5.5 GB of data.

Applied Computer Systems, 2016

This article presents an ETL (Extract, Transform, Load) prototype called Valery as alternative approach to migration process which includes a compiler for dynamic generation of SQL queries. Its main features involve: SQL dynamic generation, set of configuration commands and environment for file uploading. The tests use the Northwind academic database and an individual environment. The model implementation uses flat files and SQL as query language. Finally, there is an analysis of the results obtained.