Results 1 to 2 of 2
  1. #1
    Join Date
    Jun 2009

    Unanswered: data migration strategies.

    Hi all,

    I have a requirement to extract and migrate additional fields of data from legacy non-relational database system into the re-engineered relational database based application.

    Main requirement:

    1) To be able to accommodate the ever changing requirements for data from different clients; thus need a process to persist the newly required data that will avoid downtime of the system and has minimal effect system performance during client data retrival requests.

    Some of the options we have are as follows but not sure which is better over the other:

    2) Migrating data using the application to persist the data into the relational database.
    3) Migrating data direclty into the relational database.

    In this regard, are there any industry standards in place as this is a common issue in many enterprise applications.

    Any help in this regard is highly appreciated.

    Thanks in advance for your time and interest.

  2. #2
    Join Date
    Aug 2003
    Where the Surf Meets the Turf @Del Mar, CA
    Provided Answers: 1
    The legacy system has to be taken offline when RDBMS application is brought online.
    Otherwise you can never turn off legacy, because you have no tested RDBMS based application.
    Also, it is folly to have data entry into both system concurrently due to many data entry errors making automated comparison infeasible.
    You can lead some folks to knowledge, but you can not make them think.
    The average person thinks he's above average!
    For most folks, they don't know, what they don't know.
    Good judgement comes from experience. Experience comes from bad judgement.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts