Native database into Sql

DynamicUser

HI All
can anybody tell me how to upgrade Navision NAtive Database into sql.
Dynamic USer

Luc_VanDyck

1. Make a backup of your native Navision database using the client fin.exe
2. Use the finsql.exe client to create a new (SQL) database
3. Restore the fin.fbk you created in step 1 in this SQL database.

With the assumption that SQL Server is already installed and running, and that the Extended Stored Procedure has been added to this SQL Server (see \Sql_esp\readme.txt on the Navision Product CD).

kriki

Luc Van Dyck wrote:

1. Make a backup of your native Navision database using the client fin.exe
2. Use the finsql.exe client to create a new (SQL) database
3. Restore the fin.fbk you created in step 1 in this SQL database.

Before the backup, you better import the "migrate.fob" (you can find it in the upgrade-tools) and run it to fix the dates and other things in the DB. Eg a date 01/01/0006 is not accepted in SQL-DB. SQL only accepts dates starting from 01/01/1793 (I think).

DynamicUser

HI guys
The problem that i am facing now is that database has been restored successfully from Native Database to SQL SERVER 2005.But it doesn't show me any data in objects designer(But objects are their).But when i see through Enterprise manager 2 tables with same name has been created for each and every table.Like Customer table is created twice.
One table has a data and another one doesn't hv.

kriki

DynamicUser wrote:

HI guys
The problem that i am facing now is that database has been restored successfully from Native Database to SQL SERVER 2005.But it doesn't show me any data in objects designer(But objects are their).But when i see through Enterprise manager 2 tables with same name has been created for each and every table.Like Customer table is created twice.
One table has a data and another one doesn't hv.

In SQL a new table is created for each company. This means for each company you will have a Customer-table.
So are you sure you have only 1 company?

If this is not the case, probably your restore didn't finish completely and the data remains in other tables (in the object-designer you will see tables in the 1 000 000 000-range). In this case:Tools=>Restore. Navision asks to continue the restore. Answer yes.

DynamicUser

HI guys
After restoring the database.It gives error that

"The Microsoft Business Solutions-Navision and SQL server security system have not been synchronized successfully.

The SQl Server login 1003 doesnot exist on the SQL Server."

after this error everything has been rolled back.

Keep in mind that i am using navision 3.7 native database into sql server 2005.

Plz help me out.What should i do know?

fl

Navision 3.70 is should not be used with SQL2005, use SQL2000 instead.

The error message you gets indicates that you still should create the logins in SQL server. If not using windows authentication on SQL, you must create the same logins on SQL so that those users have rights to use SQL-server.

kriki

fl wrote:

Navision 3.70 is should not be used with SQL2005, use SQL2000 instead.

Or do a technical upgrade to 4.00SP2.

bbrown

There is a document (w1w1isql.pdf) located in the Doc folder of the Navision CD. Spend some time reading it. There is some helpful info there.

DynamicUser

HOw to do Synchronization with navision 3.7 to sql server 2000.

gvolkov

SQL 2005 server does not work well with NAV. There is an article on partnersource about this matter. You should wait till SP3 comes out in september for Navision and only then migrate to SQL 2005. Now everyone should stay on sql 2000

DynamicUser

Data has been copied successfully from 3.7 to sql server 2000.But whenever i try to open finsql it accepts cronus licence rather then client licence.When i go for licence change option client licence is already there.UPLOAD button is also disabled.

Tvis

gregoryvolkov@gmail.com wrote:

SQL 2005 server does not work well with NAV. There is an article on partnersource about this matter. You should wait till SP3 comes out in september for Navision and only then migrate to SQL 2005. Now everyone should stay on sql 2000

I cant find this article on partnersource - can you help me with a title or something?

thx

DynamicUser

when i remotely access the navision database with sql server 2000.Its not showing me servername.Is it installation mistake ?Networking is working properly.its urgent.

bbrown

Can you login by typing the servername?

DynamicUser

Yes,becoz It is not showing servername otherwise.What i hv to do to see the servername.

bbrown

Since you can connect by typing the servername, why do you need to see it in the list?

DynamicUser

Then how would system come to know about servername?

DynamicUser

We have converted our Navision 3.70 database into SQL Server 2000.But we are facing problem in performance if we are using SQL Database. The Processing of Different Priodic activity is very slow just like hanging situation. So please suggest any solution to increase the performance Using SQL DB.

bbrown

There are a couple of areas to consider when looking into performance issues. Note that these are in no particular order, and one is not more important than the other.

1. Hardware/Systems. (Including softare configuration)

This is not only what type of hardware but also how it is configure.

2. Application/Database.

At a minimum I would suggest upgrading to the latest 4.x Navision clients. This will allow you to take advantage of the newer commands (findfirst, findlast, findset).

Unless the issue is an obvious hardware configuration problem, performance issues can be somewhat involved. Focus on specific processes and identify their issues. Some things to look at are the mis-use of keys and unneeded SiftIndexes.

The available performance tools like Client Monitor and Session Monitor can be useful.

DynamicUser

HI Friends
My Client Database has been successfully converted into sql server 2000.
But now the the problem is that Code datatype in the tables doesn't show me sequencial data.Due to this the reports are not coming correctly.For ex.
Emp no is 100 after that it should show me 101,102,103.But it is showing 1001,1002 etc.

kriki

SQL doesn't know CODE-fields, so in Navision (field-property SQL Data Type) you have to tell SQL what to do with them.
If you select integer, the field will sort like an integer (actually it IS an integer), meaning you cannot put text in it.
If you select varchar (the default) it will be treated as text.
If you select variant, it should work correctly. BUT you cannot return to one of the other types.

And (I am not sure about this) it is possible all the fields that are connect (like T27."No." and T37."No." and this T15."No.") must have the same SQL-type).