"Chris" <Chris@discussions.microsoft.com> wrote in message
news:9B621EC3-33B6-4B34-939E-F0DBEDFE2D74@microsoft.com...
>
> All servers SQL2000 sp4.
>
> Have subset of tables setup in merge w/ 5 subscribers (order entry / front
> end servers). Have all tables setup in trans repl at pub to report/backup
> server, including those tables in merge w/ FE's.
>
> So request from dev to add column to a merge table, I only pickup that
> table
> is in trans repl pub, call sp_addreplcolumn w/ Trans_pub as input
> parameter
> for @publication_to_add and happily report back task is complete.
>
> Problem: we soon realize column is not on any FE server. So I realize
> mistake, drop article from Trans_pub and try to delete column to allow me
> to
> call sp_addreplcolumn w/ correct 'Merge' pub as input param.
>
> Execute alter table drop column - beep -
> Server: Msg 4932, Level 16, State 1, Line 1
> ALTER TABLE DROP COLUMN failed because 'NewCol' is currently replicated.
>
> Of course execute sp_addreplcolumn - beep -
> Server: Msg 21255, Level 16, State 1, Procedure sp_repladdcolumn, Line 101
> Column 'NewCol' already exists in table 'MyTable'.
>
> MyTable completely dropped as article from trans repl, does sql server
> think
> since MyTable is part of merge replication, that a drop column is not
> allowed
> period.
>
> How to resolve? Any ideas greatly appreciated...
>
> Chris
>

"Hilary Cotter" wrote:

> Is the column still in the merge publisher? If so, try to drop it again.
> --
> 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
>
>
>
> "Chris" <Chris@discussions.microsoft.com> wrote in message
> news:9B621EC3-33B6-4B34-939E-F0DBEDFE2D74@microsoft.com...
> >
> > All servers SQL2000 sp4.
> >
> > Have subset of tables setup in merge w/ 5 subscribers (order entry / front
> > end servers). Have all tables setup in trans repl at pub to report/backup
> > server, including those tables in merge w/ FE's.
> >
> > So request from dev to add column to a merge table, I only pickup that
> > table
> > is in trans repl pub, call sp_addreplcolumn w/ Trans_pub as input
> > parameter
> > for @publication_to_add and happily report back task is complete.
> >
> > Problem: we soon realize column is not on any FE server. So I realize
> > mistake, drop article from Trans_pub and try to delete column to allow me
> > to
> > call sp_addreplcolumn w/ correct 'Merge' pub as input param.
> >
> > Execute alter table drop column - beep -
> > Server: Msg 4932, Level 16, State 1, Line 1
> > ALTER TABLE DROP COLUMN failed because 'NewCol' is currently replicated.
> >
> > Of course execute sp_addreplcolumn - beep -
> > Server: Msg 21255, Level 16, State 1, Procedure sp_repladdcolumn, Line 101
> > Column 'NewCol' already exists in table 'MyTable'.
> >
> > MyTable completely dropped as article from trans repl, does sql server
> > think
> > since MyTable is part of merge replication, that a drop column is not
> > allowed
> > period.
> >
> > How to resolve? Any ideas greatly appreciated...
> >
> > Chris
> >
>
>