<![CDATA[<style><h1><font size="7">hp3000 migration, mpe migration, hp 3000 migration, hp3000, hp 3000, hp-e3000 migration </font></h1>
</style> ]]>
Technology
DBmotion was designed as a powerful database migration tool that is both flexible and easy to use.
To achieve this, we identified the most complex aspects involved in HP e3000 database migration and designed the product to automate these tasks.
DBmotion automatically installs its files on your server through its client-server technology. From the DBmotion client, trigger the transfer of files to your HP e3000, HP 9000 or WinTel server.
DBmotion’s flexibility lies in its client-server architecture. It supports a number of migration configurations:
- HP e3000 (TurboImage/KSAM/flat-file databases) migrated to Oracle/SQL Server on HP 9000 directly
- HP e3000 (TurboImage/KSAM/flat-file databases) migrated to Oracle/SQL Server on Windows directly
- HP e3000 (TurboImage/KSAM/flat-file databases) migrated to Oracle/SQL Server on any platform using Oracle/SQL Server Client on Windows
The DBmotion client is used to install the servers, define the migration environment, initiate the migrations and monitor their progress. After that, the HP e3000 server communicates directly with the DBmotion server, whether it is on a HP 9000 or Windows server.
As illustrated, it is not necessary for DBmotion to copy data to a PC to reach an HP 9000 server. The HP e3000 server process communicates directly with the HP 9000 server process, so there is no need for an intermediary platform using ODBC or JDBC drivers, as is the case with other products.
The DBmotion client is used to set up the environment, initiate the migration and monitor the process.
With respect to data transfer, DBmotion uses the most efficient method of copying data from the source to the target server. Using highly optimized socket routines, the HP e3000 data is pulled directly from the database and transferred through the network to reach the target server. This method is much more efficient than exporting data into files and then uploading them onto an FTP server. With DBmotion, additional disk space is not required, as the data are transferred directly through the network.
Once the data reaches the target server, DBmotion checks their integrity at an interval of records defined by the user. Rows are then inserted in bulk by talking natively to the Oracle or SQL Server database engine.
One of DBmotion’s most impressive features is its ability to separate the client from the servers. This feature, also known as a “detachable client” affords the flexibility to begin and monitor the database migration processes. This is achieved through the fact that once the database migration is initiated, DBmotion connects the source and target servers directly. From this point, the process remains independent of the DBmotion client. The user can therefore monitor the progress and status of any of the ongoing processes at any time. It is even possible to close the DBmotion client and re-start it at a later time to obtain a progress update.
|
