In some of our applications we are using SqlBulkCopy to load data into SQL Server.
After running some tracing which captures events for the Attention Event Class in SQL we have found that for each 'insert bulk' operation performed by the SqlBulkCopy WriteToServerAsync call there is a corresponding attention event raised even though these calls are successful and our client cleanly disconnections (releases the connection returning it to the pool).
Does anyone know the reason behind this? We generally use tracing of Attention events to help us identify client timeouts and the events being raised as part of the bulk copy operations pollute our logs with a bunch of attention events that seem to be benign.
thanks.
-mike
Mike Ruthruff