how to merge 2 databases

  • ..

    Thanks,
    Chinna

    Its the Journey which gives you Happiness not the Destination-- Dan Millman

  • Carefully and patiently.

    This is a tedious process, as it requires careful planning and implementation. You should first design your data mapping strategy. The most difficult part of this process is making sure the data in one database matches the types/constraints of the other. Once you have mapped everything out, you can begin adjusting the tables/data to fit the new requirements of the fully migrated database. Once you are ready to begin migrating data, I suggest you acclimate yourself with SSIS because SSIS will be your best friend during this process. SSIS provides you the scalability and flexibility to mold data to fit your needs.

  • Most importantly "Normalize" your DB when you are done. There will be a lot of redundant data as you merge your DB's.

  • More detail would be needed to provide useful answers. Does merge mean two identical structures but different data, two completely different structures but similar data, two totally different structures and utterly different sets of data? The details between these different requirements are going to dictate totally different approaches. A few commonalities will exist. Even if you assume totally different structures and completely different data, it's doubtful that that will be absolute. There are probably commonalities. These will need to be identified and then treated as if it were one of the other two approaches.

    If you want more precise help, provide more detail about what you're hoping to achieve and what your starting point is.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • And then there's the subject of primary keys... especially if they're based on IDENTITY.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply