How to run a large script from sqlcmd and continue despite errors

Question

I am on SQL Server 2008 R2.
I have  a large sql file (4 GB size) which has various insert  statements created by genarate script of SQL Server 2008, i.e, generate script facility to create insert satements for data of all the tables in a database.
Now I am loading this data in another database, so I use a command like:
sqlcmd -S "10.37.59.6"  -d  JnJ_Version1   -U admin_dtyler10 -P xxxxxxx  -i "D:\stage\JnJ-Version1\Data.sql" -o D:\stage\JnJ-Version1\idatasql.out -V 17
This command is run from a task scheduler and after 3 hours task comepletes and the
idatasql.out  contains following error message:
Msg 102, Level 15, State 1, Server AMAZONA-658CHN2, Line 42
Incorrect syntax near ')'.
Before this message there were lot of success messages such as:
(1 rows affected)
Processed 1299500 total records
(1 rows affected)
Processed 1299600 total records
(1 rows affected)
Processed 1299700 total records
(1 rows affected)
Processed 1299800 total records
1. Now how do I troubleshoot this error message, my file is so big...
2. Also how sqlcmd handles errors, I know there are many insert satements followed by GO, so
I aussme if there wer errors that GO transaction will fail, but it will continue with next insert satement after GO ,  is that correct If not, how can I make it contnue despite errors.
I did not see any option in sqlcmd to do that.
3. Also what does -V17 in Sqlcmd do. I had copied it from somewhere on internet.

Answer 1

1. Now how do I troubleshoot this error message, my file is so big...
Finding the error in a 4GB is certainly a challenge. The easiest is probably to write your own C# program that parses out the batches and submits them - and spews out the bat ones.
2. Also how sqlcmd handles errors, I know there are many insert satements followed by GO, so
I aussme if there wer errors that GO transaction will fail, but it will continue with next insert satement after GO ,  is that correct If not, how can I make it contnue despite errors.
Yes, SQLCMD will continue with the next batch, unless the error was raised with state 127. But see below.
3. Also what does -V17 in Sqlcmd do. I had copied it from somewhere on internet.
I did SQLCMD -? and I see that -V is related to severitylevel. It may mean that SQLCMD will exit if the severity level is >= 17. But I would recommend that you look up SQLCMD in Books Online yourself to verify. (Yes, I am too lazy to do it myself this
time.)
Erland Sommarskog, SQL Server MVP, [email protected]