I’m aware that some data imports, subject to certain conditions, will be very fast because they leverage a “copy” command in the DB rather than process the data imports rows line-by-line.
I can’t find this discussed anywhere in Nextworld Help but would like to know what the conditions are that need to be met for a data import leverage that capability. Can someone point me in the right direction?
The source for this is hidden within server code. It changes occasionally as we see bugs or different handling scenarios.
As of right now, the following must be satisfied:
Copy command needs to not be disabled for the environment (Unlikely this is the case, unless we have major issues with the COPY command such ops disables it across the system)
Data Import Definition
Data Import Mode: Insert
Cannot have logic blocks specified, except for Post-File logic blocks
Error tolerance: “All or nothing” or “All or nothing, by file”
Cannot have attachment mappings specified
Cannot have external link mappings specified
Destination Table
Cannot be workflow enabled
Cannot be used as an active cube V1 or summary table data source