Post reply

SSIS Script Error - The value is too large to fit in the column data area of the buffer.

  • May 16, 2009 at 3:47 pm

    #155715

    I have an input DB, then script, then Output to DB.

    It fails on the script with the above error.

    My input and output columns are set to nvarchar(max), null.

    Any suggestions ?

    Thanks

  • May 17, 2009 at 5:28 am

    #995970

    Hello,

    Did you already spot his thread? May be the suggestions contained will work for you as well.

    http://social.msdn.microsoft.com/forums/en-US/sqlintegrationservices/thread/e95c1fda-bedb-4a8b-b90d-12c6c8779b30/

    Regards,

    John Marsh

    www.sql.lu
    SQL Server Luxembourg User Group

  • May 17, 2009 at 6:33 am

    #995985

    Hi John,

    Thanks for your suggestion!

    I read the thread and changed the maxconcurrentexecutables from (-1) to (1) with no improvement:(

    Any other ideas ?

    Regards

    Ian

  • May 17, 2009 at 6:46 am

    #995986

    Hello Ian,

    That’s a shame.

    A couple of posters in the same thread stated that deleting and recreating the Scripts fixed their problems. May be worth a try if there’s no other logical explanation?

    Regards,

    John

    www.sql.lu
    SQL Server Luxembourg User Group

  • May 17, 2009 at 8:50 am

    #996012

    Hi John,

    After reading the MS threads i went in the wrong direction;(

    I did some backtracking and found that although my DB I/O fields were nvarchar(max)

    the field in the script under output, was only 50.

    Once i changed this field to 1000 everything worked fine 🙂

    Thanks again for your help!

    Regards

    Ian

  • May 17, 2009 at 9:13 am

    #996022

    Good to hear that it worked out in the end 🙂

    www.sql.lu
    SQL Server Luxembourg User Group

  • January 16, 2014 at 3:33 pm

    #1680901

    I was encountering the same problem and checked my script component column length was 50, which was causing the problem. When I set it at 500, it worked like a charm. Thank you guys.

  • January 16, 2014 at 3:38 pm

    #1680902

    isuckatsql (5/17/2009)

    Hi John,

    After reading the MS threads i went in the wrong direction;(

    I did some backtracking and found that although my DB I/O fields were nvarchar(max)

    the field in the script under output, was only 50.

    Once i changed this field to 1000 everything worked fine 🙂

    Thanks again for your help!

    Regards

    Ian

    I was encountering the same problem and checked my script component column length was 50, which was causing the problem. When I set it at 500, it worked like a charm. Thank you guys.

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply