Hi all!
I have a task to import NAV2015 company to an existing database, which can be done with import-navdata cmdlet. The problem is that this procedure is very slow. It lasts for 10-12 hours to import 10GB navdata. Now, I have to import even larger database so I'm expecting to last it longer, if it can be done at all.
I've checked through sql profiler to see what is done in import-navdata operation and, imho, can say that microsoft did all what it could to make it optimal. It uses insert bulk operations with tablock. It also strips all indexes/visfts before import and recreates them after.
What can be done to speedup this or, is there any new idea how to merge two companies from different dbs?
What bugs me is that the same database (part of migration) was imported with fbk (NAV2009) much faster, in 2 hours. What is so different between these version so fbk import is 6x faster that import-navdata?
I have a task to import NAV2015 company to an existing database, which can be done with import-navdata cmdlet. The problem is that this procedure is very slow. It lasts for 10-12 hours to import 10GB navdata. Now, I have to import even larger database so I'm expecting to last it longer, if it can be done at all.
I've checked through sql profiler to see what is done in import-navdata operation and, imho, can say that microsoft did all what it could to make it optimal. It uses insert bulk operations with tablock. It also strips all indexes/visfts before import and recreates them after.
What can be done to speedup this or, is there any new idea how to merge two companies from different dbs?
What bugs me is that the same database (part of migration) was imported with fbk (NAV2009) much faster, in 2 hours. What is so different between these version so fbk import is 6x faster that import-navdata?