SqlBulkCopy::SqlRowsCopied Event
Occurs every time that the number of rows specified by the NotifyAfter property have been processed.
Assembly: System.Data (in System.Data.dll)
Note that the settings of NotifyAfter and BatchSize are independent. Receipt of a SqlRowsCopied event does not imply that any rows have been sent to the server or committed.
You cannot call SqlBulkCopy.Close (Close) or SqlConnection.Close (Close) from this event. Doing this will cause an InvalidOperationException being thrown, and the SqlBulkCopy object state will not change. If the user wants to cancel the operation from the event, the Abort property of the SqlRowsCopiedEventArgs can be used. (See Transaction and Bulk Copy Operations for examples that use the Abort property.)
No action, such as transaction activity, is supported in the connection during the execution of the bulk copy operation, and it is recommended that you not use the same connection used during the SqlRowsCopied event. However, you can open a different connection.
The following console application demonstrates how to bulk load data using a connection that is already open. The NotifyAfter property is set so that the event handler is called after every 50 rows copied to the table.
In this example, the connection is first used to read data from a SQL Server table to a SqlDataReader instance. Note that the source data does not have to be located on SQL Server; you can use any data source that can be read to an IDataReader or loaded to a DataTable.
Important |
|---|
This sample will not run unless you have created the work tables as described in Bulk Copy Example Setup. This code is provided to demonstrate the syntax for using SqlBulkCopy only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL INSERT … SELECT statement to copy the data. |
Available since 2.0
