Prev: Howto find the Name of Logreader and Distribution Task
Next: SQL replication/indexes- 2005 Publisher, 2000 Subscribers
From: M Bourgon on 4 Dec 2009 14:38
ultra short version: I need a way to delete a particular command (in
the system tables) that's not applying correctly.

Long version:
I added a table to replication while there was a DDL trigger on the
database. That trigger did not deal well with the particular
ARITHABORT options, and choked while trying to add an article to
publication. The problem that I now have is that I'm getting the
following error:

(Transaction sequence number: 0x00001BD900000051008C00000000, Command
ID: 6)

Error messages:
Target string size is too small to represent the XML instance (Source:
MSSQLServer, Error number: 6354)
Get help: http://help/6354
Target string size is too small to represent the XML instance (Source:
MSSQLServer, Error number: 6354)
Get help: http://help/6354


I've dropped that article and recreated the replication while the
trigger is off, but that's queued up behind the bad commands. How do
find and delete this bad command?
From: Paul Ibison on 4 Dec 2009 17:42
As a stop-gap you could use the profile to continue on data consistency
errors and add 6354 to the skiperrors command.
HTH,
Paul Ibison

From: M Bourgon on 7 Dec 2009 12:54
On Dec 4, 4:42 pm, "Paul Ibison" <Paul.Ibi...(a)ReplicationAnswers.Com.
(donotspam)> wrote:
> As a stop-gap you could use the profile to continue on data consistency
> errors and add 6354 to the skiperrors command.
> HTH,
> Paul Ibison

Thanks, Paul. I'd also found a way to delete the rows involved, but
wound up not needing either.

After viewing the browser commands using sp_browsereplcmds, I figured
out the problem. The schemas commands for replication (running the
schema script) were too long for the DDL trigger we had set up on the
target database. For some reason eventdata() couldn't cope with it.
Which is a major bummer, since we'd been setting up DDL triggers for
auditing, and they worked great... except for this issue and another
with maintenance.

Disabled the DDL trigger and it successfully applied the schema, and
was good to go.

Thanks for the help.
M
 | 
Pages: 1
Prev: Howto find the Name of Logreader and Distribution Task
Next: SQL replication/indexes- 2005 Publisher, 2000 Subscribers