Solved

Error when updating

Posted on 2014-04-09
6
181 Views
Last Modified: 2014-04-12
Getting the following

Internal error. Buffer provided to read column value is too small. Run DBCC CHECKDB to check for any corruption.

When updating a table between 2 servers/databases.

Can't find a solution.

Any ideas?
0
Comment
Question by:JElster
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
6 Comments
 
LVL 39

Expert Comment

by:Pratima Pharande
ID: 39988482
Try ou some of below

1. Rebuild Indexex
2.update package 2 for SP2
3. parse the SQL statement the old fashioned way
Refer for more details
http://www.sqlservercentral.com/Forums/Topic287524-149-1.aspx
0
 
LVL 1

Author Comment

by:JElster
ID: 39988504
What does parse the sql statement the oldfashion way mean.
I rebuilt the indexes.. still same error
0
 
LVL 69

Expert Comment

by:Scott Pletcher
ID: 39988825
Did you run "DBCC CHECKDB"?  What were the results?
0
Simplifying Server Workload Migrations

This use case outlines the migration challenges that organizations face and how the Acronis AnyData Engine supports physical-to-physical (P2P), physical-to-virtual (P2V), virtual to physical (V2P), and cross-virtual (V2V) migration scenarios to address these challenges.

 
LVL 1

Author Comment

by:JElster
ID: 39988903
What am I looking for

CHECKDB found 0 allocation errors and 0 consistency errors in database
0
 
LVL 75

Expert Comment

by:Anthony Perkins
ID: 39990438
Can you elaborate on your system and post the relevant code that is triggering the error?
0
 
LVL 69

Accepted Solution

by:
Scott Pletcher earned 500 total points
ID: 39992216
Hmm, interesting.

I suggest flushing the procedure/statement cache for that db, since there may be an obsolete object definition being used somewhere.

You'll need to get the database_id for that db:

DBCC FLUSHPROCINDB(<database_id>);


Also, I'd refresh all views in the db -- it won't hurt, and it might, with some luck, help:

EXEC sp_refreshview 'viewname'
0

Featured Post

PeopleSoft Has Never Been Easier

PeopleSoft Adoption Made Smooth & Simple!

On-The-Job Training Is made Intuitive & Easy With WalkMe's On-Screen Guidance Tool.  Claim Your Free WalkMe Account Now

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

INTRODUCTION: While tying your database objects into builds and your enterprise source control system takes a third-party product (like Visual Studio Database Edition or Red-Gate's SQL Source Control), you can achieve some protection using a sing…
In this article I will describe the Copy Database Wizard method as one possible migration process and I will add the extra tasks needed for an upgrade when and where is applied so it will cover all.
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …

751 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question