transformations:exportdb
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
transformations:exportdb [2021/02/12 06:58] – dmitry | transformations:exportdb [2021/02/12 07:02] – dmitry | ||
---|---|---|---|
Line 3: | Line 3: | ||
Exports the current dataset into the database table which name is specified either explicitly or using a [[: | Exports the current dataset into the database table which name is specified either explicitly or using a [[: | ||
- | Note that the operation effectively //appends// rows to existing ones. If you need to remove old data use the [[sqlcommand|Database command]] action. If you need to update rows, use the [[transformations: | + | Note that the operation effectively //appends// rows to the target table. If you need to remove old data use the [[sqlcommand|Database command]] action. If you need to update rows, use the [[transformations: |
===Performance=== | ===Performance=== | ||
- | Under the hood, the exporting is performed using SQL INSERT statements by batches of 10 or 100 or 1000 rows. Exporting in bigger batches can be slightly | + | Under the hood, the exporting is performed using SQL INSERT statements by batches of 10, 100, 1' |
Some databases have a performance bottleneck for batches of SQL INSERT statements which may lead to slow performance (especially on wide tables). Consider using the [[transformations: | Some databases have a performance bottleneck for batches of SQL INSERT statements which may lead to slow performance (especially on wide tables). Consider using the [[transformations: |
transformations/exportdb.txt · Last modified: 2023/10/14 16:20 by craigt