I had a SSIS package where I was calling a stored
procedure in OLEDB Source and it was returning a “The
Value Was Too Large to Fit in the Output Column” error.
Well, My Datatype in OLEDB source was matching with my
OLEDB Destination table. However, when I googled, we got solutions like to
increase the output of OLEDB Source using Advanced Editor option. I was not
at all comfortable with their solution as my source, destination and my
intermediate transformation all are having same length and data type and I don’t
want to change.
Then I found that I was missing SET NOCOUNT ON option was missing in
Stored Procedure. Once I added it, my data flow task ran successfully.
Thank you for introducing like this tool. keep it update.
ReplyDeleteBest Msbi Online Training
Msbi Online Training in Hyderabad