Share via

SqlBulkCopy.SqlRowsCopied Event


Occurs every time that the number of rows specified by the NotifyAfter property have been processed.

 event Microsoft::Data::SqlClient::SqlRowsCopiedEventHandler ^ SqlRowsCopied;
public event Microsoft.Data.SqlClient.SqlRowsCopiedEventHandler SqlRowsCopied;
member this.SqlRowsCopied : Microsoft.Data.SqlClient.SqlRowsCopiedEventHandler 
Public Custom Event SqlRowsCopied As SqlRowsCopiedEventHandler 
Public Event SqlRowsCopied As SqlRowsCopiedEventHandler 

Event Type


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.


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.

using Microsoft.Data.SqlClient;

class Program
    static void Main()
        string connectionString = GetConnectionString();
        // Open a sourceConnection to the AdventureWorks database.
        using (SqlConnection sourceConnection =
                   new SqlConnection(connectionString))

            // Perform an initial count on the destination table.
            SqlCommand commandRowCount = new SqlCommand(
                "SELECT COUNT(*) FROM " +
            long countStart = System.Convert.ToInt32(
            Console.WriteLine("NotifyAfter Sample");
            Console.WriteLine("Starting row count = {0}", countStart);

            // Get data from the source table as a SqlDataReader.
            SqlCommand commandSourceData = new SqlCommand(
                "SELECT ProductID, Name, " +
                "ProductNumber " +
                "FROM Production.Product;", sourceConnection);
            SqlDataReader reader =

            // Create the SqlBulkCopy object using a connection string. 
            // In the real world you would not use SqlBulkCopy to move
            // data from one table to the other in the same database.
            using (SqlBulkCopy bulkCopy = new SqlBulkCopy(connectionString))
                bulkCopy.DestinationTableName =

                // Set up the event handler to notify after 50 rows.
                bulkCopy.SqlRowsCopied +=
                    new SqlRowsCopiedEventHandler(OnSqlRowsCopied);
                bulkCopy.NotifyAfter = 50;

                    // Write from the source to the destination.
                catch (Exception ex)
                    // Close the SqlDataReader. The SqlBulkCopy
                    // object is automatically closed at the end
                    // of the using block.

            // Perform a final count on the destination 
            // table to see how many rows were added.
            long countEnd = System.Convert.ToInt32(
            Console.WriteLine("Ending row count = {0}", countEnd);
            Console.WriteLine("{0} rows were added.", countEnd - countStart);
            Console.WriteLine("Press Enter to finish.");

    private static void OnSqlRowsCopied(
        object sender, SqlRowsCopiedEventArgs e)
        Console.WriteLine("Copied {0} so far...", e.RowsCopied);
    private static string GetConnectionString()
    // To avoid storing the sourceConnection string in your code, 
    // you can retrieve it from a configuration file. 
        return "Data Source=(local); " +
            " Integrated Security=true;" +
            "Initial Catalog=AdventureWorks;";


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.

Applies to