SQL Migration - questions on Code Field Information

Cindy101

Hello All,

First off - if this has been address already sorry for the repeat, but I couldn't find information on it when forum searching.

So I'm reaching (hopefully) the tail end of my first NAV upgrade, from 3.6 to 5.0 sp1. The end result will be a shiny new NAV DB running on SQL Server. I've just gotten through running the migrate.fob and I'm to the section in the documentation about checking the Code type NAV fields. I've got some questions regarding this (some may stem from not having extensive knowledge of SQL server in general). Well here goes

1) Is this necessary? The documentation mentions numbering conflicts and I suppose that is because SQLServer sorts varchar differently than NAV sorts Code type?

2) From reading the doc it seems I'm OK with changing each field that has "Numeric Only"=TRUE, "Compatible Integer"=TRUE, and "Zero Padded"=FALSE to SQLServer Integer type? Now what if those check boxes differ between companies?

3) The documentation mentions 3 important tables/fields
- "G/L Account"."No."
- "Acc. Schedule Line"."Row No."
- "VAT Statement Line"."Row No."
Now for most companies I have zero padded = TRUE on both "G/L Account"."No." and "Acc. Schedule Line"."Row No.". and many have Numeric Only = FALSE.
Oh right, there was a question coming about all of this somewhere... So do I need to be very worried about these, what is a good way to fix them?

4)In the documentation it says "If any of these fields appear in the Numbering Conflicts window, you should be aware that any totals based on them may be inconsistent." This worries me.. Should my end result be all the fields in the list have "Numbering conflict"=FALSE?

and the last question

5) The changes I make to this form, they will be implemented when I do the native backup and then the SQL restore?

Sorry for the wall of text, and thanks very much in advance for help!

Cindy101

Bump bump, anyone? [-o<

I went ahead with the migration, hoping everything works out OK...

ara3n

That's a lot of questions. Go through the migration.

You need to look the fields of type code. If the field length is the same, then you should be fine.
Otherwise you will need to change the sql data type. This will only work if the Code is only numeric.

Make sure you can print the account schedules and you get the same numbers.

You'll have to fix all the bad dates.

Otherwise you should be fine.

Cindy101

Thanks for the reply!

The client/testers are going over the DB now, I told them to look through the account schedules and see if anything looks fishy. So far so good!