Hi Team,
I followed this link to export and import data in Microsoft Dynamics Navision 2013.
But I find a big issue.
When I try to import a 110MB data to an existing database, the original database size is 22GB, after finished, the database file size increased to 59GB.(No include log file size).
Then I did a second test, I tried to import an 25GB data to an existing database, the original database size is 22GB, I only finished 32%, and the database file size increased to 320GB. So I have to cancel the importing process.
What I missed? Why it processed so slow and eat so much disk capacity?
*This post is locked for comments
Yesterday, I tired to import the 25GB .navdata file again, the .ndf file increased to 630GB, and only finished 51%. I think the file size is too big to accept. There should have some reason.
No, I have tried to set the recovery model to simple and bulk-logged model, but it is same.
And the size I means is the .ndf file.
data in a file does not mean it will be equal data in a database. A database creates indexes and they take a lot of space. the data in the file is zipped and data in a database is not.
Do you have recovery model = full in your database? If so, the log is growing because it logs every transaction.
However, if you perform a full backup, then the log is shrinked and must return to the size set by the administrator.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,253 Super User 2024 Season 2
Martin Dráb 230,188 Most Valuable Professional
nmaenpaa 101,156