"Pranil" wrote:

> I have set up an Updateable Subscriber replication between databases A and B.
> This creates and uses the MSreplication_queue system table in the destination
> (B) database.
>
> I have lot of other tables being replicated from A to B, all standard
> Transactional replication. e.g. Table C is replication from A to B,
> transaction replication. When I dropped the publication for table C from A,
> it dropped the following objects in B as well:
> MSreplication_queue
> MSrepl_queuedtraninfo
>
> This caused the Updateable Subscription to fail. I got around this by
> creating another (dummy) Updateable Subscriber replication which recreated
> the above tables, and then dropped the dummy publication.
>
> This sounds like a serious bug, because why would dropping a simple
> transactional replication drop these two tables, especially since dropping an
> UPDATEABLE SUBSCRIBER replication doesn't touch these tables AND a
> transactional publication has nothing to do with these tables ??
>
> We did not experience this problem in SQL 2000.
>
> Has anyone else come across this problem ? Is there a fix for it, as it's
> causes a serious problem is our organisation because a critical process