mas Tri
2010-10-29 09:34:27 UTC
Hi all,
I have set a merge replication on my database, which distributor and
publisher reside on same server. My server use MS SQL Server 2005.
to minimize data downloaded to subscriber, I use row (horizontal)
filtered replication. as consequences, some tables, published on many
publication, partitioned by replication filter.
AFAIK, MS SQL replication use trigger to keep track changes, so I
assume that each publication inject its own trigger into published
tables. It means, table published on more than publication will have
also many replication triggers.
everything running well until I drop one of publication. After I drop
replication, I can only send SELECT query. any insert, delete and
insert will return error with message: "invalid objext name
MSmerge_repl_view_XXX", with XXX is some guid number, id of dropped
publication I presume.I have tried both SQL Management Studio and SMO
object called from my .NET application.
It seems that replication trigger is not cleanly cleared.
Would anybody here help me and share, what's wrong with my
publication ?
tri
jakarta, indonesia.
I have set a merge replication on my database, which distributor and
publisher reside on same server. My server use MS SQL Server 2005.
to minimize data downloaded to subscriber, I use row (horizontal)
filtered replication. as consequences, some tables, published on many
publication, partitioned by replication filter.
AFAIK, MS SQL replication use trigger to keep track changes, so I
assume that each publication inject its own trigger into published
tables. It means, table published on more than publication will have
also many replication triggers.
everything running well until I drop one of publication. After I drop
replication, I can only send SELECT query. any insert, delete and
insert will return error with message: "invalid objext name
MSmerge_repl_view_XXX", with XXX is some guid number, id of dropped
publication I presume.I have tried both SQL Management Studio and SMO
object called from my .NET application.
It seems that replication trigger is not cleanly cleared.
Would anybody here help me and share, what's wrong with my
publication ?
tri
jakarta, indonesia.