BatchInsert: Difference between revisions
Jump to navigation
Jump to search
John Leavitt (talk | contribs) No edit summary |
John Leavitt (talk | contribs) No edit summary |
||
| Line 6: | Line 6: | ||
===Description=== | ===Description=== | ||
Determines if the import queries are executed individually or in batches to improve performance. Each batch will contain approximately 1000 queries and by default will be executed in its own transaction. A query batch will contain all the queries to import a number of import types (incident, problem, system, etc). For very large imports with more than 1000 queries per import type the batch will be split at 1000 queries and may not contain all the queries to import an import type. | Determines if the import queries are executed individually or in batches to improve performance. Each batch will contain approximately 1000 queries and by default will be executed in its own transaction. A query batch will contain all the queries to import a number of import types (incident, problem, system, etc). For very large imports with more than 1000 queries per import type the batch will be split at 1000 queries and may not contain all the queries to import an import type. | ||
Default value: | |||
No: Import individually (Default value) | |||
Yes: Import in batches | |||
Revision as of 23:55, 12 February 2015
XML Element
<BatchInsert></BatchInsert>
Description
Determines if the import queries are executed individually or in batches to improve performance. Each batch will contain approximately 1000 queries and by default will be executed in its own transaction. A query batch will contain all the queries to import a number of import types (incident, problem, system, etc). For very large imports with more than 1000 queries per import type the batch will be split at 1000 queries and may not contain all the queries to import an import type.
No: Import individually (Default value)
Yes: Import in batches