Extremely easy way to bulk insert data into SQL Server using SqlBulkCopy class

[@Tanghero123]

Thanks for the video. I used this for one of our projects and found it to be quite efficient. The only downside is that you need to be extra careful with things that might cause an error like duplicate primary keys, as sqlBulkCopy does not return good error messages when something goes wrong. - Chris T.

[@DotNetCoreCentral]

Great point, thanks!

[@tayyabbhatti6781]

@@DotNetCoreCentral to eliminate this issue, you have to first count the total records by executing the query. then loop start from the count to the length. this will help you

[@liamhotspur9182]

I love your videos, simple and straight!

[@DotNetCoreCentral]

thanks!

[@sreenuksr]

I am following your series. nice videos and explanation. Wish you happy new year.

[@DotNetCoreCentral]

Thanks! And wish you a Happy New Year!

[@efimtenkin1641]

Thank you, you helped me a lot

[@DotNetCoreCentral]

Glad I could help!

[@sravs3054]

Awesome

[@zulfiqar7967]

We can do it bulk insert in sql query itself.. it’s very safe and good performance..

[@coding-gemini]

Excellently explained, thanks for the video. Can you create a video for bulkupdate if any ?

[@DotNetCoreCentral]

Thanks!

[@pardhasaradhi0076]

I have a question. Iam using bulkcopy but i would like to return identity row. Please suggest

[@Thalapraga]

Can it be used for bulk insert of 10 million rows?

[@Proviper666]

Can some one help? System.InvalidOperationException: 'The ConnectionString property has not been initialized.' EDIT: I solved by adding direct connection string. string connectionString = "Data Source=.;Initial Catalog=YourDBname;Integrated Security=True;"; using var connection = new SqlConnection(connectionString);

[@TommiLipponen]

Dear Sir, can this method be used for to copy hundreds of thousands rows from CSV file to MSSQL database?

[@DotNetCoreCentral]

Yes, you can first read the CSV file in chunks, add the data o the data table, and then bulk upload. I will suggest using chunks of 1000 records or some number like that to avoid memory as well as SQL Server timeout issues. But that will depend on the complexity of the data structure.