SplitTransaction

XML Element


Description
Determines if insert queries are run in one transaction or split into multiple transactions.

SplitTransaction settings:

Batch: Each batch of queries will run in its own transaction. This is the default value when BatchInsert is enabled, and is an invalid setting when BatchInsert is not enabled. This setting allows for any batch of queries to fail while still successfully importing the remaining batches. If this setting is enabled (“Yes”) and if one type has a failure and another is imported successfully, the imported file and import log will appear in the Error section of the Data Import page.

Type: Each import type (incident, problem, etc) in the file will be run in its own transaction. Not available for batch inserts. This setting is useful when importing a large number of types without batch import enabled, as it prevents an error in one type from rolling back the entire import. If this setting is enabled (“Yes”) and if one type has a failure and another is imported successfully, the imported file and import log will appear in the Error section of the Data Import page.

NoSplit: All queries will be run in one transaction even if BatchInsert is enabled or there are multiple import types in one file. This is the default value when BatchInsert is disabled. This setting allows for rolling back the entire import if an error occurs anywhere.

Yes: If BatchInsert is enabled, each batch will be inserted in its own transaction. This setting is invalid if BatchInsert is not enabled (set to “No”).

No: All queries will be run in one transaction (Default Value)