Conversion of Native datbase to SQL Server

upasanisandip

Hi all,
Which is the easiest method to transfer native database to SQL Server ?
Is there any readymade tool for this?


Thanks,
Sandip.

kriki

There is a tool called Migrate.fob. This can be found in the upgrade toolkits. You need it to check your database to search for values (e.g. dates) that cannot be handled in SQL. Once you have run it and fixed it, your DB is ready for SQL.
After that make a Navision backup.
With the finsql.exe you make a Navision-DB in SQL and you restore your backup.
After that you can start working on performance. If you put the Navision objects unaltered in SQL, it will work but it will be slow. You will need to finetune the indexes for SQL and this is not something to do for beginners.

Waldo

kriki wrote:

...
After that you can start working on performance. If you put the Navision objects unaltered in SQL, it will work but it will be slow. You will need to finetune the indexes for SQL and this is not something to do for beginners.

And I can back him up in this one!!

Marije_Brummel

There are specialists for this. :whistle:

vyanku

Very good information :whistle:

Waldo

Mark Brummel wrote:

There are specialists for this.
_________________
Mark Brummel
MVP Microsoft Dynamics Nav | SQL Perform Consultant

What do you mean?

mggoswami

sir twhere can i get migrate.fob to migration native data to sql server 2005

kriki wrote:

There is a tool called Migrate.fob. This can be found in the upgrade toolkits. You need it to check your database to search for values (e.g. dates) that cannot be handled in SQL. Once you have run it and fixed it, your DB is ready for SQL.
After that make a Navision backup.
With the finsql.exe you make a Navision-DB in SQL and you restore your backup.
After that you can start working on performance. If you put the Navision objects unaltered in SQL, it will work but it will be slow. You will need to finetune the indexes for SQL and this is not something to do for beginners.

kine

This can be found in the upgrade toolkits

It is part of Upgrade toolkit. This toolkits can be downloaded from PartnerSource. If you are end-user, you need to contact your partner.

GoMaD

It could be that the objects in the migrate.fob need to be adjusted to check text field for special characters.

baldaum

Hi,

I have the same problem. Converting the dates fields works fine with the migrate.fob
But I have mayn special characters in the NAV native database and when importing into SQL Server it generates an error.

Can anyone tell me how to adapt the migrate.fob to find and solve the special characters?

Many thanks
Markus

kine

If I look into NAV 2009 Migrate.fob into codeunit 104011, there is this code:

CheckText(FieldName : Text[80];MaxLength : Integer;VAR Value : Text[250])
IF ChangeMode THEN BEGIN
  IF FindRangeError(FieldName) THEN
    EVALUATE(Value,RangeCheckEntry."New Value");
  EXIT;
END;
IF STRLEN(Value) > MaxLength THEN BEGIN
  Value2 := COPYSTR(Value,1,MaxLength);
  WriteRangeError(FieldName,COPYSTR(Value,1,250),Value2);
END;

You can add own testing there to test the text for problematic characters.

And the error on SQL is connected to Collation you have selected for the DB...

Waldo

You could try to uncheck the "Validate Code Page" on the Alter Database window. But that wouldn't mean it will import the characters correctly .. it's just not giving you the errors anymore... .

baldaum

Hi,

I have founf the error. We had one articel in our item table, which was not correct after the move from NAV 4.0 SP3 to NAV 5.0 SP1.
The item description was a french wine name and we had very strange characters in this field. Every other articel (we have many french special characters in our tables) had no problem and the import was working fine after correction.

What I did: I just changed this article description in the original NAV 4 db to a common "a" and then everything was working fine. No problem with the rest of the special characters. Strange, but it worked.

Many thanks
Markus

DenSter

Good catch, and thanks for the feedback.