Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

replication Error: MSSQLServer, Error number: 8152 Expand / Collapse
Author
Message
Posted Thursday, June 5, 2014 11:54 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, July 24, 2014 11:31 PM
Points: 3, Visits: 32
i apologize if this in the wrong place.

i have a replication job publishing to 7 other instances, on one of the instances synchronization fails due to the following error:
String or binary data would be truncated. MSSQLServer, Error number: 8152. what is stumping me is both tables only contain integer data types and as far as i can tell are completely the same, any help would be greatly appreciated.
Post #1578144
Posted Sunday, June 8, 2014 8:09 AM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Monday, November 24, 2014 5:46 AM
Points: 4,031, Visits: 7,172
Any chance you have a trigger on the table in one of the subscribers?

______________________________________________________________________________
"Never argue with an idiot; They'll drag you down to their level and beat you with experience"
Post #1578655
Posted Wednesday, June 18, 2014 10:09 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, July 24, 2014 11:31 PM
Points: 3, Visits: 32
no but i do have 3 triggers on the published table?
Post #1583536
Posted Wednesday, June 18, 2014 10:28 PM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Monday, November 24, 2014 5:46 AM
Points: 4,031, Visits: 7,172
Just a shot, but try temporarily disabling the triggers to see if the issue goes away. And I'm curious, what do these triggers do?

I've also seen situations where extremely long object names (i.e. index names, table, or stored-procedure names) causing this. I can't remember where I read it but if I remember correctly there is a limit on the column that holds the "alter" command is limited to 4000 characters, whereas in many cases the text that contains your stored-procedure or index can be considerably larger.

You may want to look at that as well if disabling the triggers doesn't help you


______________________________________________________________________________
"Never argue with an idiot; They'll drag you down to their level and beat you with experience"
Post #1583538
Posted Wednesday, June 25, 2014 4:32 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, July 24, 2014 11:31 PM
Points: 3, Visits: 32
disabling the triggers did not work. if helps to see, here is the command its breaking on;

Command attempted:
create procedure [dbo].[sp_MSins_dbot_TABLEName_msrepl_ccs]
@c1 int,
@c2 int,
@c3 int
as
begin
if exists (select *
from [dbo].[t_TABLENAME]
where [TableID] = @c3)
begin
update [dbo].[t_TABLENAME] set
[ItemID] = @c1,
[DescriptorGroupID] = @c2
where [TableID] = @c3
end
else
begin
insert into [dbo].[t_TABLENAME](
[ItemID],
[DescriptorGroupID],
[TableID]
) values (
(Transaction sequence number: 0x0000001900009E25006400000000, Command ID: 52)

Error messages:
String or binary data would be truncated. (Source: MSSQLServer, Error number: 8152)
Get help: http://help/8152
Post #1586187
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse