THE SQL Server Blog Spot on the Web
Welcome to SQLblog.com - The SQL Server blog spot on the web Sign in | Join | Help
in Search

Need a shortterm and midterm solution for two different database

Last post 06-03-2008, 9:48 by Adam Machanic. 1 replies.
Sort Posts: Previous Next
  •  05-31-2008, 11:52 7090

    Need a shortterm and midterm solution for two different database

    Hello guys,

    I have to write business solution for shortterm and new term.

    Scenario like this.

    There are two companies one is in JAPAN and other one is in UK they both making bikes.

    Now they merger togather, CEO is asking  the HRM department to have data of employees.

    Now company 1 is having won XP workstation with IBM DB2 databse server and company 2 is having Mysql databse with lynux operating system terminals.

    Now management strategy is:

    Company is going to keep their old system working on but i have to provide solution which would merge those two databse and make a report of both companies employee name, id and so on and that would be the short  term solution.[here i think federated databse connection]

    For mid term solution i have to make mydatabase ditributed so i dont have to save data in two different databses.

    I am clear that what i have to do but i have questions like:

    Do i need to change schema of the database ?

    and how i can make report over this two solution. i have to add list of requirements for the integration of data and creation of the report

    also a proposed solution togather with my justification for the advice and a plann meeting the short term requirement, including en evaluation of the existing database approch and federated databse.

     

    I would be much appericiate if some master mnd can advice me where to start ....

    Please help me...

    Thanks in advance..

    Filed under: , ,
  •  06-03-2008, 9:48 7114 in reply to 7090

    Re: Need a shortterm and midterm solution for two different database

    I would probably start by looking at a data replication technology; support two-way replication to begin with, then slowly migrate away from the database platform they no longer support.  This way all of the existing reporting and querying infrastructure will still work during the transition period; no reason to mess around with cross-database queries, federated servers, and the like.

Powered by Community Server (Commercial Edition), by Telligent Systems
  Privacy Statement