|
Data
|
The DataInserter type exposes the following members.
Properties
| Name | Description | |
|---|---|---|
|
AttemptBulkInsert | Get or set to attempt use of a BULK INSERT on a destination SQL Server connection |
|
|
AttemptTruncateTable | Set to True to attempt use of a TRUNCATE TABLE on a destination SQL Server connection if ClearDestinationTables is True and it looks like the referential integrity definition supports this. Your SQL Server connection will need the rights to perform this operation. |
|
|
BulkInsertEncoding | This setting defines the text encoding that will be used when writing a temporary BULK INSERT file that will be needed if a SQL Server BULK INSERT is performed - make sure the encoding output matches the specified CODEPAGE value in the BulkInsertSettings property. |
|
|
BulkInsertFilePath | This setting defines the file path that will be used when writing a temporary BULK INSERT file that will be needed if a SQL Server BULK INSERT is performed - make sure the destination SQL Server has rights to this path. |
|
|
BulkInsertSettings | This setting defines the SQL Server BULK INSERT settings that will be used if a BULK INSERT is performed. |
|
|
ClearDestinationTables | Set to True to clear all data from the destination database before processing data inserts. |
|
|
DelimiterReplacement | This specifies the string that will be substituted for the field terminator or row terminator if encountered in a database value while creating a BULK INSERT file. The field terminator and row terminator values are defined in the BulkInsertSettings property specified by the FIELDTERMINATOR and ROWTERMINATOR keywords respectively. |
|
|
ExcludedTables |
Get list of tables to be excluded during data processing
(Inherited from BulkDataOperationBase) |
|
|
ForceBulkInsert | Get or set to force use of a BULK INSERT on a destination SQL Server connection regardless of whether or not it looks like the referential integrity definition supports this. |
|
|
ForceTruncateTable | Set to True to force use of a TRUNCATE TABLE on a destination SQL Server connection if ClearDestinationTables is True regardless of whether or not it looks like the referential integrity definition supports this. Your SQL Server connection will need the rights to perform this operation |
|
|
FromSchema |
Get or set Source schema
(Inherited from BulkDataOperationBase) |
|
|
PreserveAutoIncValues | Set to True to preserve primary key value data to the destination database before processing data inserts. |
|
|
RowReportInterval |
Get or set number of rows to process before raising progress events
(Inherited from BulkDataOperationBase) |
|
|
Timeout |
Get or set Maximum number of seconds to wait when processing a SQL command before timing out.
(Inherited from BulkDataOperationBase) |
|
|
ToSchema |
Get or set destination schema
(Inherited from BulkDataOperationBase) |
|
|
UseFromSchemaReferentialIntegrity |
Get or set - use referential integrity information from source/to destination database during data processing
(Inherited from BulkDataOperationBase) |
|
|
WorkTables |
These are the tables that were found in both source and destination to be used for data operation...
(Inherited from BulkDataOperationBase) |
See Also