I have been working on implementing DDL Triggers, to monitor changes
in our environment. However, it doesn't seem to behave with
Replication - at the very least, it chokes when new tables are added.
Does anyone have any suggestions or workarounds?

The only fix I've found is to disable/delete the trigger, let it
apply, then enable/create the trigger. Not an ideal solution.


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


Command attempted:
create procedure [sp_MSins_dbomyreplicatedtable]
@c1 int,@c2 char(11),@c3 char(13),@c4 char(11),@c5 char(11),@c6 char
(14),@c7 char(30),@c8 char(60),@c9 char(30),@c10 char(25),@c11 char
(1),@c12 int,@c13 char(1),@c14 decimal(19,5),@c15 char(11),@c16 char
(4),@c17 decimal(11,3),@c18 char(2),@c19 int,@c20 decimal(14,3),@c21
decimal(19,2),@c22 decimal(19,5),@c23 decimal(19,5),@c24 decimal
(19,5),@c25 char(1),@c26 char(1),@c27 char(1),@c28 char(2),@c29 char
(1),@c30 datetime,@c31 char(1),@c32 datetime,@c33 datetime,@c34 char
(Transaction sequence number: 0x00002CDC000002B6015B00000000, Command
ID: 13)