Post reply

data too large for specified buffer

  • January 31, 2005 at 3:43 pm

    #68039

    I have a DTS package that updates a table of about twenty fields from a view.   We have had to make a change to a 'Decription' field.  It went from a text field (14) to varchar (100).  The problem I have is I get an error refering to the 'Description' field saying data from field is too large for specified buffer. 

    How do I specify how large the buffer size is?

    Where do I do this?

    Is this a global setting?

    What other things might I impact by changing this setting?

    Is there a work around to this problem?  

    Thank You 

  • January 31, 2005 at 3:57 pm

    #539827

    Try running sp_refreshview on the view.

  • February 1, 2005 at 4:25 pm

    #540058

    I ran sp_refreshview and the problem is still present. The view works fine. When do a select statement on it returns the expected data. It's only inside the DTS package where gives the error message.

  • February 1, 2005 at 4:56 pm

    #540062

    Are the data sources all SqlServer, or are any of them Jet 4.0 ?

    http://support.microsoft.com/default.aspx?scid=kb;en-us;281517

     

     

  • February 4, 2005 at 12:55 pm

    #540764

    All sources are SQL Server

  • March 11, 2005 at 11:01 am

    #546692

    Can't offer any solutions for you, can only commiserate.

    Have  a DTS package that simply copies records from one table to another inside the same database.  Datatypes for all fields match.  If I run this on SQL 2000 (any SP) on Windows 2000, with any version of MDAC 2.7 or later, there is no problem.  When I try to execute on Windows XP SQL 2000 SP3 with MDAC 2.81, fails with the Buffer Overrun problem.  The column that causes the problem is "ntext" datatype.

    Windows XP SQL 2000 SP3 MDAC 2.71 works.

    Am still searching for any info that might help.  If I find something I will try posting here for you.

    Would appreciate any helpful info anyone else has on this.

    Thanks.  Good luck.

  • March 15, 2005 at 6:29 pm

    #547189

    I ended up changing the field types from text to varchar. After the change the problem cleared up.  I see this as work around and not a solution.  I am running windows 2k with Mdac 2.8 but i'm not sure if that would be a cause to this problem.  Anyway ... Good Luck!

  • March 16, 2005 at 7:02 am

    #547248

    Thanks for the update.

    I managed to come up with a work around as well.  I was able to write an SP that did the job with no problem.  I automated running that.

    The underlying problem is still there, but I was wasting too much time looking for the cause.

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

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