Comments on: SSIS Variables Do Not Like Varchar(MAX)

By: Gibson

Gibson — Tue, 23 Aug 2011 20:15:44 +0000

I just attempted this with an ADO.Net connection instead of OLEDB and the results were no different. It still fails with ADO.Net.

By: Johnny

Johnny — Fri, 29 Jul 2011 10:05:00 +0000

SOLUTION:

This is a limitation of OLEDB.
Use ADO.net connection rather than OLEDB connection.

By: Abhi

Abhi — Mon, 04 Apr 2011 06:22:11 +0000

I want to print more than 8000 character in my store procedure so i am using varchar(max) instead of varchar(8000). But still it is showing only 8000 characters. Please help me how to get all characters.

By: SSIS and the limit of 8000 chars in a string variable | BI-Bloggers

SSIS and the limit of 8000 chars in a string variable | BI-Bloggers — Sun, 26 Sep 2010 17:35:43 +0000

[...] then found this blog entry http://blog.boxedbits.com/archives/6 (Langstons’s answer) which led to a working solution although it is more a [...]

By: Peter

Peter — Wed, 03 Feb 2010 10:52:04 +0000

Actually, I am trying to do just that with a 600 char varchar (from a varchar(1000) field) string, and it is failing.

The SQL-string is loading well in the Object Variable, together with some ID fields. When I display the Object contents the string is shown complete and correct. The next step is to loop through the rows in the Object variable. There, each row is read and fed to separate variables. This step is not working, the foreach loop can’t seem to read the long string properly, and when I MsgBox the variable it just shows a blank.

Jamies blog posts are no longer available either (I saved hyperlinks instead of downloading the pages…).

Any ideas ?

By: Langston

Langston — Wed, 08 Jul 2009 18:26:10 +0000

.ToString() doesn’t work. See my post below for a solution.

By: Langston

Langston — Wed, 08 Jul 2009 18:25:30 +0000

See my post below for solution.

By: Langston

Langston — Wed, 08 Jul 2009 18:24:28 +0000

@Tom VdP: You have to assign it to an Object variable because the string variable will not accept varchar(max) result sets. I found that the .ToString() method doesn’t work after you save the result set to an SSIS object variable. All that does is return the data type, not the value of the string itself.

@Tom VdP: Rather than use a script task to execute the SQL, which is more extensive to code and less modular, I found a simpler approach.

To All,
Basically, you have to use a ForEach Loop to “shred” the object variable saved from the SQL Task. See here for details on how to do that (credit Jamie Thompson – SSIS guru): http://blogs.conchango.com/jamiethomson/archive/2005/07/04/SSIS-Nugget_3A00_-Execute-SQL-Task-into-an-object-variable-_2D00_-Shred-it-with-a-Foreach-loop.aspx

Once you have your varchar(max) results saved to the Object variable, you loop through it, which in some cases will be only once if all you needed was a single string value in the first place. In the loop’s variable mappings, you map the results from the object variable to an SSIS string variable, and VIOLA! The string value from your varchar(max) result set is now saved to an SSIS string variable.

The strange part is that I do not know why the ForEach loop properly stores the string value of the varchar(max) result set to an SSIS string variable, but you cannot do it in a script task. But hey, this works, so I aint complaining. BTW, this workaround is confirmed in SSIS 2008, although I cannot imagine it would not work in 2005.

By: Tom VdP

Tom VdP — Wed, 11 Mar 2009 19:45:43 +0000

Valentin, are you sure you need an Object variable ? Anyway, try the .ToString() method, that should do it, I would say.

By: Tom VdP

Tom VdP — Wed, 11 Mar 2009 19:43:45 +0000

Indeed, the SSIS Exec SQL Task is too limited. We ran into this limitation too and worked around it by using a Script Task to execute the SQL. Strings in the Script Tasks are not limited to that silly 8000 characters limit.