Hello,
We are beginning the migration of Navision 3.7 to 4.03, first we make a Navision back up, after we convert the 3.7 Database to 4.0, then we create a new 4.0 database. May be we can have the problem here, because we have a 55Gb Database and it is recommended to create a double size dabatase, but regarding space issues we create a database of 70Gb. When we run the restore everything seems all right but it tooks 24hs and it had not finished yet. So, we stop it and then the SQL instance stops working, but it is another story...
My question is, anybody has done a Navision Restore? How long it takes? and regarding the database size may be someone had have the same problem.
Thank you for your time!!!
Matias
0
Comments
My Blog - nav.education
Hi Matias, I fully understand your situation. Actually I am in a very similar situation.
Last week I decided to go for a trip on my bike, and in the end, after riding all day and all night, I still was not there. I am not sure why. So I ask you "how long should it take me to get there on my bike"?
The part that takes the most time is building indexes and SIFT tables, and that gets multiplied exponentially if you have a large number of companies, so it sounds to me like you have a database with many of those. Of course it is all speculation on my part.
RIS Plus, LLC
Sorry, long day yes that's exactly what I mean.
You say that you made the database 70 GB, but how large did you make the transaction log? Auto-expansion of the transaction log during the restore can have a sizable impact on time to restore. Expand the transaction log large enough so it does not need to expand during the restore. I tend to go 150-200% of DB size. Also be sure the log is on its own dedicated disk. (RAID 1)
Even with this it is not uncommon for restores of large databases to take 20+ hours.
I like that suggestion.
Almost certainly you need to start again. Even if you worked it out (doing some SQL magic), you would never be sure that the data was valid.
OK.. all again! :evil: , well... I ask for a final suggestion: our old database was 55Gb of database_1.mdf file, 1Gb database.mdf and 1Gb database_Log.ldf, What's your suggestion about file size. I was thinking that a good one could be database_1.mdf = 110Gb, database.mdf = 2Gb and database_Log.ldf = 110Gb. Any idea?
Leave the mdf at about 200Meg, but create an ndf file about 120 Gig. Log 110 should be enough, but if you have multiple companies or something like that, then it may need more. Remember that after the restore you can possibly shrink your Log file somewhat.
OK, Thank you very much sir!.. I will try it... When it finishes I will tell you how well it was.. (I hope so.. )
I have create it and I restore the Navision back up on it, the day next Navision is wating me with a sign sayng "Table Data 50018 does not exist" and then it exit. :shock:
I found that it is a view, I don't understand how can I view it in Navision?.. The only solution that I think is deleting it and doing the backup again..
How can I solve this ??!!
Check that 50018 is not a linked table this will give that error, we had this problem and solved it by Creating the database, then we restored the objects from the backup, by going to Object Designer, Import and pointing it to the backup and not a fob file, then when this was done we ran the restore, it treated it as a data only backup, no faster but no errors!
David
Mobile: +44(0)7854 842801
Email: david.cox@adeptris.com
Twitter: https://twitter.com/Adeptris
Website: http://www.adeptris.com