SQL Backup & Restore

Bokk

We are working with an SQL database and took a backup using the Navision backup function (which documentation says is possible). We then created a new SQL DB to restore to and ran the Navision restore function. We were able to open the DB, but when we try to bring up various forms, etc. many throw an error message that "The flowfield value cannot be calculated." and it indicates we have to define and activate key fields and it gives some specific info as to which ones. I looked at the keys and they appear to be there, but only the primary key is enabled, the rest are not.

Is this an issue between the Navision and the SQL or something else?

Thanks in advance,

kine

It seems for me that you restore the backup into Navision native DB, not to SQL db... in this case you need more keys for calcualting SUMS than in SQL DB...

DenSter

The last part of the Navision restore process creates and activates all the right keys. It looks to me like the restore process was not completed fully. I'd wipe out the new database and run the restore again.

By the way, you should create the database using the Navision interface. I know it is possible to use EM, but it is just safer to use Navision. I know how to do it in EM myself, but I always use Navision just to make sure I don't screw it up.

Bokk

When we created the new SQL DB we did use the Navision interface and filled in all our parameters, etc on the various tabs. This seemed to work fine. We then connected to that DB using File -> Database -> Open and ran the restore function so I am quite sure the restore is going into the correct DB. We did try this 3 times and also did the backup again in case that didn't grab all the keys the first time - same results each time.

The DB is a fair size (about 10 Gb). Could the size of the DB cause issues for the Backup/Restore functions in Navision?

Thanks for your input!

DenSter

I don't know, I have never seen this before. I would probably try creating a new backup file, since this one is obviously not working.

Did someone disable the keys before running the backup from the original database? I hope you don't have to re-activate the keys manually, thass a lotta work!

Johan_Gullberg

I tried to do what you did and got the same result.
Then took a SQL backup instead, created a new database and restored the backup into the new database. Don´t forget to change the paths to *.mdf *.ndf and *.ldf. ..otherwise it will point to the same location as the database you backuped.

We are working with an SQL database and took a backup using the Navision backup function (which documentation says is possible).