"bchu" <bchu@discussions.microsoft.com> wrote in message
news:8DBF72FD-2631-4029-852E-0875D547BFFC@microsoft.com...
> Dear all,
>
> Currently I am working on a immediate updating subscriber for transaction
> replication. After solving the MSDTC issue, I got an error "Could not
> change
> the publisher because the subscription has been dropped. Use
> sp_subscription_cleanup to clean up the triggers". After reading a
> previous
> post, I make sure the two tables are having the same collations. But the
> error still exist. What could be the problem?
> Thank you!
>
> CREATE TABLE [Supervisory] (
> [Member] [varchar] (50) COLLATE Chinese_Taiwan_Stroke_CI_AS NOT NULL ,
> [Supervisor] [varchar] (50) COLLATE Chinese_Taiwan_Stroke_CI_AS NULL ,
> [Activate] [bit] NOT NULL ,
> [msrepl_tran_version] [uniqueidentifier] NOT NULL CONSTRAINT
> [DF__Superviso__msrep__17036CC0] DEFAULT (newid()),
> CONSTRAINT [PK_Supervisory] PRIMARY KEY CLUSTERED
> (
> [Member]
> ) ON [PRIMARY]
> ) ON [PRIMARY]
> GO
>
> CREATE TABLE [Supervisory] (
> [Member] [varchar] (50) COLLATE Chinese_Taiwan_Stroke_CI_AS NOT NULL ,
> [Supervisor] [varchar] (50) COLLATE Chinese_Taiwan_Stroke_CI_AS NULL ,
> [Activate] [bit] NOT NULL ,
> [msrepl_tran_version] [uniqueidentifier] NOT NULL CONSTRAINT
> [DF__Superviso__msrep__17036CC0] DEFAULT (newid()),
> CONSTRAINT [PK_Supervisory] PRIMARY KEY CLUSTERED
> (
> [Member]
> ) ON [PRIMARY]
> ) ON [PRIMARY]
> GO
>
>

"Hilary Cotter" wrote:

> Can you check to see if the Subscription really has been dropped?
>
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
>
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
>
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
>
>
> "bchu" <bchu@discussions.microsoft.com> wrote in message
> news:8DBF72FD-2631-4029-852E-0875D547BFFC@microsoft.com...
> > Dear all,
> >
> > Currently I am working on a immediate updating subscriber for transaction
> > replication. After solving the MSDTC issue, I got an error "Could not
> > change
> > the publisher because the subscription has been dropped. Use
> > sp_subscription_cleanup to clean up the triggers". After reading a
> > previous
> > post, I make sure the two tables are having the same collations. But the
> > error still exist. What could be the problem?
> > Thank you!
> >
> > CREATE TABLE [Supervisory] (
> > [Member] [varchar] (50) COLLATE Chinese_Taiwan_Stroke_CI_AS NOT NULL ,
> > [Supervisor] [varchar] (50) COLLATE Chinese_Taiwan_Stroke_CI_AS NULL ,
> > [Activate] [bit] NOT NULL ,
> > [msrepl_tran_version] [uniqueidentifier] NOT NULL CONSTRAINT
> > [DF__Superviso__msrep__17036CC0] DEFAULT (newid()),
> > CONSTRAINT [PK_Supervisory] PRIMARY KEY CLUSTERED
> > (
> > [Member]
> > ) ON [PRIMARY]
> > ) ON [PRIMARY]
> > GO
> >
> > CREATE TABLE [Supervisory] (
> > [Member] [varchar] (50) COLLATE Chinese_Taiwan_Stroke_CI_AS NOT NULL ,
> > [Supervisor] [varchar] (50) COLLATE Chinese_Taiwan_Stroke_CI_AS NULL ,
> > [Activate] [bit] NOT NULL ,
> > [msrepl_tran_version] [uniqueidentifier] NOT NULL CONSTRAINT
> > [DF__Superviso__msrep__17036CC0] DEFAULT (newid()),
> > CONSTRAINT [PK_Supervisory] PRIMARY KEY CLUSTERED
> > (
> > [Member]
> > ) ON [PRIMARY]
> > ) ON [PRIMARY]
> > GO
> >
> >
>
>