Challenge: Nav 26 native to sql server 2008

lecocqelecocqe Member Posts: 6
edited 2010-07-17 in Navision Financials
Hello,

this is my first post in this forum.

i try to do the following: upgrade nav 26 database to sql server 2008.

what i already did is:

backup with navision + try to restore but i have an error linked to sql server:
"The current ANSI or OEM Code Page on your computer does not match the code page on the server" ??

any suggestion or links ?

thank you in advance,

ELE

Comments

  • einsTeIn.NETeinsTeIn.NET Member Posts: 1,050
    "Money is likewise the greatest chance and the greatest scourge of mankind."
  • lecocqelecocqe Member Posts: 6
    thank you,

    but which one do i have to use ?
    i read the links that you gave me but it's not clear yet.µ

    ELE
  • lecocqelecocqe Member Posts: 6
    Hello,

    I changed my way to do it.

    from 2.6E Native DB, i opened a 4.0sp1 client and converted to 4.0sp1.
    and i followed the procedure to migrate to sql server...

    i used a tools package available here. but i had problems with migrate.fob. Codeunit 104015 is missing when i import this.
    i used migrate.fob from 2.6 version.

    i'm now restoring the things but still problem with data inconsistencies.

    I keep this forum informed.

    regards
  • BeliasBelias Member Posts: 2,998
    do you just want to migrate from native to sql?
    in that case, you don't need migration tools. (at least, you didn't say that you want to upgrade the executable, too)
    P.S.: does nav 2.6 work on sql2008?
    -Mirko-
    "Never memorize what you can easily find in a book".....Or Mibuso
    My Blog
  • lecocqelecocqe Member Posts: 6
    Hello,

    My first try: direct conversion from 2.6 to SQL server 2008 (express) gave sql poblems.

    My second try: i opened 2.6 db with 4.0sp1 client, it proposes to convert to 4.0 native i said "Yes"

    thus, i have now a 4.0sp1 db that i want to convert to sql database. i'm following for this purpose the pdf from upgrade tools kit 4.0
    there i had a problem with a code unit 104015 (from migrate.fob) that was not present when i want to import the fob.

    i have to use this fob because the documentation says that i have to use it becasue of dates in sql server.

    for the moment, i'm correcting data inconsistencies before taking a bkp and restoring in sql mode.

    regards,

    ELE
  • BeliasBelias Member Posts: 2,998
    lecocqe wrote:
    i have to use this fob because the documentation says that i have to use it becasue of dates in sql server.
    Didn't know about this, let someone enlight us...
    anyway, what do you want to do?keep your db on nav2.6 or not?if you convert the db to 401, it won't be (easily and safely) downgradable back to 2.6, do you know it?
    -Mirko-
    "Never memorize what you can easily find in a book".....Or Mibuso
    My Blog
  • David_SingletonDavid_Singleton Member Posts: 5,479
    There is an enhanced version of migrate.fob on this site somewhere. Search for it.

    On the other hand, how many upgrades have you done like this before? if you have not done a lot it might be better to get someone in to help you.
    David Singleton
  • lecocqelecocqe Member Posts: 6
    it's not for production.

    i want to have this db converted to sql to easily make some reporting about history data.

    i will search for this migrate.fob

    regards,
Sign In or Register to comment.