I have a NAV 2015 navdata file that I extracted from the LIVE system at customer site.
When I try to import this on my developer server using the exact same version on a SQL 2016 the database grows to enormous sizes.
the navdata file is 2.8 GB - a fairly small database.
I have tried all sorts of things - currently the import is working on import of company no 2 from that file and the database file (.mdf) has grown to 85GB and the transaction log has grown to 15GB - and is has been running for quite a few hours now.
These sizes make absolutely no sense to me.
If i do the same import job on a SQL 2012 - it runs smoothly - no big issues, database files or long import times.
Have anybody experienced this kind of behaviour on SQL 2016 and knows which properties or settings to tweak to make the import work?
Poul Lindholm Christiansen
/ +45 4050 9306