The message:

gives you a fairly strong clue as to what the problem is, I think. This is not package-related, rather it relates to the SQL instance...

Try using a UNC path rather than a mapped drive.

miles_lesperance (11/19/2013)

---

I was able to work through the issue, and can now get all of the rows to be inserted. The file that I was trying to import did not...

Out of interest, can you briefly explain why you are using ADO rather than OLE DB?

Let you know ... what?

Can it be done? Yes.

Will we do it for you? No.

Will we help with questions? Yes - though you'll get better responses if you...

skosanabv (11/19/2013)

---

I found the solution

I experienced the same Issue with my packages, and tried all these solutions posted here, but none of them worked for me.

What I then did:

1. SQL...

Have a look here[/url] and see whether it helps.

If not, please explain a little about why you want to do this to give us some background.

No problem, thanks for posting back 🙂

You just answered a five-year-old post - hope that...

Koen Verbeeck (11/18/2013)

---

I think the limit in SSIS is smaller.

I've had issues with very large SQL statements in Execute SQL Tasks, but they were less than 64K...

Batch size.

Have a look at this page. All sorts of useful info on limits there, including max. batch size.

Nomvula (11/17/2013)

---

thank you Phil for the quick response

i've managed to find the error after going through my script task over and over again and found that i didn't assign the...

Have you tried putting a breakpoint in the script task and then stepping through it line by line to determine exactly which row is generating the error? Might help you...

I have a string variable which stores a big set of sql statements, ie insert statements. The insert statement intends to inserts about 200K rows with 10 columns (Lots !)

I...