I’m importing a 4.5 million row file from a SQL Server to another one for further analysis. The process stops every time there’s a truncation error.
I use Notepad++ to go to the row and see where the problem is. If it’s just a cell shift, I fix it, if not I delete the row, and start the import again. So far the error was once every 4-500 thousand rows.
I was able to get 3.2 million rows imported, but I keep getting these truncation error messages. I am sure that there must be a SQL command to tell SQL Server to skip those rows while importing so I don’t have to start the import again every 2 hours.
I still have 1.5 million rows to import. How can I tell SQL Server to skip the row and go to the next one?
Or can I do it in Visual Studio? I used to work with SQL statement a very long time go, so I am quite a novice…
Francesco is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
3