db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Update of "MysqlDerbyMigration/RequirementDocument" by RaminMoazeni
Date Tue, 13 Jun 2006 04:05:35 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by RaminMoazeni:
http://wiki.apache.org/db-derby/MysqlDerbyMigration/RequirementDocument

------------------------------------------------------------------------------
  
  === 3.2 System Requirements ===
  
-  * '''CR-1:''' The system should use MySQL as the source DBMS and Apache Derby as the target
DBMS.
-  * '''CR-2:''' The system should be made in such a way to accept the configuration parameters
using a configuration file.
-  * '''CR-3:''' Migration tool needs to be installed on either the source or target DBMS.
-  * '''CR-4:''' The user should be able to select a schema to be migrated from the source
DBMS.
-  * '''CR-5:''' The migration tool should display information from source RDBMS related to
tables, views and stored procedures.
-  * '''CR-6:''' The user should be able to select object types to be migrated from the source
DBMS. 
-  * '''CR-7:''' Users should be notified about the objects that were not successfully converted.
-  * '''CR-8:''' The user should be provided with a summary report at the end of the migration
process.
-  * '''CR-9:''' The errors that the system encounters should be logged in the form of an
error log.
+  * '''CR-1:''' The system should use MySQL as the source DBMS and Apache Derby as the target
DBMS. The clients clearly defined that at minimum the migration tool shall migrate data from
MySQL to Apache Deby.
+  * '''CR-2:''' The system should be made in such a way to accept the configuration parameters
using a configuration file. In the absence of GUI, the system shall be able to read configuration
information such as database identification parameters, etc from configuration file.
+  * '''CR-3:''' Migration tool needs to be installed on either the source or target DBMS.
The migration tool needs to be installed on either the source or target DBMS to reduce network
traffic overhead.
+  * '''CR-4:''' The user should be able to select a schema to be migrated from the source
DBMS. The user should be able to pick and choose the schema that needs to be migrated from
the source DBMS to the target DBMS. The user will be shown a list of schemas from the source
DBMS.
+  * '''CR-5:''' The migration tool should display information from source RDBMS related to
tables, views and stored procedures. The migration tool shall display information related
to column and index information for each table in the source database, along with information
on stored procedures and views.
+  * '''CR-6:''' The user should be able to select object types to be migrated from the source
DBMS. The user should be able to select object types such as tables, views and stored procedures
that need to be migrated. 
+  * '''CR-7:''' Users should be notified about the objects that were not successfully converted.
The users need to be notified about any unsuccessful object conversions, so that the SQL CREATE
statements would be manually edited.
+  * '''CR-8:''' The user should be provided with a summary report at the end of the migration
process. At the end of the migration process, a summary report of the migration will be displayed
to the user containing detailed description of the objects that have been migrated.
+  * '''CR-9:''' The errors that the system encounters should be logged in the form of an
error log. There will be a log file which will contain all the exceptions and errors that
occurred during the processing of the source DBMS, during startup, migration, etc. 
  

Mime
View raw message