From c065dbb563bd127f7f07a3c73accee5d36844f06 Mon Sep 17 00:00:00 2001 From: Wraith2 Date: Thu, 20 Apr 2023 00:15:34 +0100 Subject: [PATCH] docs change --- doc/snippets/Microsoft.Data.SqlClient/SqlBulkCopy.xml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/snippets/Microsoft.Data.SqlClient/SqlBulkCopy.xml b/doc/snippets/Microsoft.Data.SqlClient/SqlBulkCopy.xml index 87f7cc5e99..06fdf1b5b6 100644 --- a/doc/snippets/Microsoft.Data.SqlClient/SqlBulkCopy.xml +++ b/doc/snippets/Microsoft.Data.SqlClient/SqlBulkCopy.xml @@ -503,14 +503,15 @@ and faster to use a Transact-SQL `INSERT … SELECT` statement to copy the data. property. - + event and does not imply that this number of rows has been sent to the server or committed. This value can be accessed during or after the execution of a bulk copy operation. -This value can become negative if the number of rows exceelds int.MaxValue. If this may happen use the RowsCopied64 property. +This value will wrap around and become negative if the number of rows exceeds int.MaxValue. Consider using the property. ]]>