Posts: 2,481
Threads: 1,434
Joined: Mar 2010
This project aims to bring up the idea of automation of transfer of data structure (table) designs as well as data (records) from one DBMS to another (possibly different type of) DBMS across the network. The system has a source side (client) and destination side (server) parts. At the source side, the user selects a given RDBMS (say Oracle, MS SQL server, DB2, Sybase etc.) and interrogates to get a list of tables present in the system. He chooses a table, selects the columns of the table to migrate and sets up a filter condition for the records to pick. The user also specifies the destination RDBMS system (need not be the same type as the source) The definition of the table selected and its records are read by the application, converted into XML form and transmitted to the destination side application (server) using the network. The destination side application receives the XML files, parses them and creates the required tables and records in the destination RDBMS
he project becomes very useful for an administrator who wishes to switch from one DBMS system to another. The entire data conversion becomes reliable, fast and efficient. These findings proved that Migration of database from a source machine to a destination machine is a very helpful application
Posts: 2,300
Threads: 878
Joined: Sep 2010
: Database Migration over Network
ABSTRACT
Title: Database Migration over Network
Objective:
This project aims to bring up the idea of automation of transfer of data structure (table) designs as well as data (records) from one DBMS to another (possibly different type of) DBMS across the network. The system has a source side (client) and destination side (server) parts. At the source side, the user selects a given RDBMS (say Oracle, MS SQL server, DB2, Sybase etc.) and interrogates to get a list of tables present in the system. He chooses a table, selects the columns of the table to migrate and sets up a filter condition for the records to pick. The user also specifies the destination RDBMS system (need not be the same type as the source) The definition of the table selected and its records are read by the application, converted into socket object and transmitted to the destination side application (server) using the network. The destination side application receives the Object, parses them and creates the required tables and records in the destination RDBMS
The project becomes very useful for an administrator who wishes to switch from one DBMS system to another. The entire data conversion becomes reliable, fast and efficient. These findings proved that Migration of database from a source machine to a destination machine is a very helpful application.
Migration .
a. Oracle to Oracle
b. Csv to oracle
c. Normal text file to oracle
d. Access to Oracle
e. Oracle to csv
f. Oracle to access
Software Requirements:
Operating System : Windows
Graphical User Interface : Java Swing, AWT.
Application Logic : Java 7 (Socket Programming).
Database : Oracle, Ms Access, My SQL.
Applications : MS Excel.
Protocols : TCP (Transaction control Protocol).
IDE/Workbench : My Eclipse 6.0.
Hardware Requirements:
System Configuration
Processor : Pentium III – 900 MHz
Hard Disk : 20 GB
RAM : 128 MB
Posts: 1
Threads: 0
Joined: Feb 2011
i want brief explanation of this project
Posts: 1
Threads: 0
Joined: Apr 2011
Actually sir, i am facing problem in our major project the title is, DATABASE MIGRATION OVER NETWORK ,so can you please give your contact number so can come to insitiute.
Posts: 2,051
Threads: 1,405
Joined: Jun 2011
[attachment=14957]
ABSTRACT:
Title: Database Migration over Network
Objective:
This project aims to bring up the idea of automation of transfer of data structure (table) designs as well as data (records) from one DBMS to another (possibly different type of) DBMS across the network. The system has a source side (client) and destination side (server) parts. At the source side, the user selects a given RDBMS (say Oracle, MS SQL server, DB2, Sybase etc.) and interrogates to get a list of tables present in the system. He chooses a table, selects the columns of the table to migrate and sets up a filter condition for the records to pick. The user also specifies the destination RDBMS system (need not be the same type as the source) The definition of the table selected and its records are read by the application, converted into socket object and transmitted to the destination side application (server) using the network. The destination side application receives the Object, parses them and creates the required tables and records in the destination RDBMS
The project becomes very useful for an administrator who wishes to switch from one DBMS system to another. The entire data conversion becomes reliable, fast and efficient. These findings proved that Migration of database from a source machine to a destination machine is a very helpful application.
INTRODUCTION
Database migration:
It may be necessary to move from one database vendor to another, or to upgrade the version of database software being used. The latter case is less likely to require a physical data migration, but this can happen with major upgrades. In these cases a physical transformation process may be required since the underlying data format can change significantly. This may or may not affect behavior in the applications layer, depending largely on whether the data manipulation language or protocol has changed - but modern applications are written to be agnostic to the database technology so that a change from Oracle to My SQL, DB2 or SQL Server should only require a testing cycle to be confident that both functional and non-functional performance has not been adversely affected.
A method of migrating a database from a first server to a second server while continuing to provide transaction service, the method comprising the steps of: providing transaction service on the first server; establishing a database copy on the second server; logging at least one transaction from the first server to create a transaction log; executing the at least one logged transaction on the second server; repeating the steps of logging at least one transaction and executing the at least one logged transaction on the second server until a set point is met; queuing at least one transaction request; executing the at least one queued transaction request on the second server; and providing transaction service on the second server; wherein a time duration of each repeating step is necessarily shorter than a preceding repeating step, and transaction service on the second server is paused until the providing step
Posts: 6
Threads: 0
Joined: Aug 2010
Thanks for your post. please post some more topics................
Posts: 1
Threads: 0
Joined: Oct 2011
Plz.. send Project Report and other material on Data Migration project...
Posts: 6,566
Threads: 1,107
Joined: Jul 2011
to get information about the topic"Database Migration over Network" please refer page link bellow
http://studentbank.in/report-database-mi...er-network
Posts: 1
Threads: 0
Joined: Jan 2012
I wan 2 download this seminars.
Posts: 6,566
Threads: 1,107
Joined: Jul 2011
to get information about the topic"Database Migration over Network" please refer page link bellow
http://studentbank.in/report-database-mi...er-network
Posts: 3
Threads: 2
Joined: Nov 2011
14-03-2012, 08:50 PM
i want source code...........................
Posts: 4,190
Threads: 817
Joined: Feb 2012
please full project of the database migration secutity over network
