migration 2.60 to 4.0 SP1

hazem
hazem Member Posts: 187
edited 2006-02-10 in Navision Attain
Hello,
we made a database migration from the version 2.60 to the 4.0 SP1. Now, The problem is that the information contained in the database in v2.60 has changed during the migration process, and reinserting it in the new one is not the right way i think :x So we decided to import the FOB file containing all objects of database in the new vesion 4.0 (after migration) into the original database (of v2.60) in order to maintain the current information, stored in the database. BUT there are a lot of errors such us unknown variables... How should i proceed? :-k

Comments

  • kriki
    kriki Member, Moderator Posts: 9,121
    If I understand it correctly, during the upgrade process (=upgrading the data), users continued working on the old DB?
    When doing the upgrade process of the data, they shouldn't work, because the things they did will be lost.
    Once you start the process:
    -customer stops working
    -make a backup of the data
    -do the upgrade
    -do some checks to see if the upgrade went well
    -install the new DB and users only start to work at that moment and with the new version.

    BTW: some tables have been changed a lot between 2.60 and 4.00. So you just can't import a 4.0 fob in a 2.60 DB. Also because 4.00 has new commands that 2.60 doesn't know.
    Regards,Alain Krikilion
    No PM,please use the forum. || May the <SOLVED>-attribute be in your title!

  • hazem
    hazem Member Posts: 187
    All right,i think the error is that they continued working on the DB during the migration. So if i understand,the only way to use the current information with the migrated database is to reinsert ALL of it, which is "impossible"!!
  • ara3n
    ara3n Member Posts: 9,258
    Final upgrade is done during weekend. During which time they do no make any changes to the database. Otherwise they have to reenter the data in new version.
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
  • DenSter
    DenSter Member Posts: 8,307
    here's the steps for the migration:
    1 - stop using the 'old' system for ever!! nobody gets to use it anymore until eternity.
    2 - convert the data and create the 'new' one. I'm skipping all the work steps. During this time nobody, I repeat, NOBODY, does ANY kind of transaction in ANY of the two systems. NOBODY gets to use either one of the systems during this time
    3 - start using the 'new' system only.

    This simply takes time, but must be done if you want to do it right.
    Daniel Rimmelzwaan
    RIS Plus, LLC

Categories