Problem dropping a column from a table in a publication

Hi,
I create a column in a table that is in a merge publication with this code
USE JMI
GO
sp_repladdcolumn @.source_object='ztest',@.column='dateDepart',@.typet ext='
datetime NULL DEFAULT getDate()' ,@.publication_to_add='JMI_articles'
GO
I realise that a made a mistake and i want to drop the column
So i try this code
USE JMI
GO
sp_repldropcolumn @.source_object='ztest',@.column='dateDepart'
GO
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'JMI_articles' because schema replication is performed.
Server: Msg 5074, Level 16, State 1, Line 1
The object 'DF__ztest__dateDepar__66D9612E' is dependent on column
'dateDepart'.
Server: Msg 4922, Level 16, State 1, Line 1
ALTER TABLE DROP COLUMN dateDepart failed because one or more objects access
this column.
It is possible to drop a column from a replication ?
Yes, it is possible, however in this case it looks like other tables are
dependent on this column, so you it looks like you have to drop the
constraint before you do this.
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
"GC" <GC@.discussions.microsoft.com> wrote in message
news:DEFC493F-23E9-40C3-816D-6ADFE710581C@.microsoft.com...
> Hi,
> I create a column in a table that is in a merge publication with this code
> USE JMI
> GO
> sp_repladdcolumn @.source_object='ztest',@.column='dateDepart',@.typet ext='
> datetime NULL DEFAULT getDate()' ,@.publication_to_add='JMI_articles'
> GO
> I realise that a made a mistake and i want to drop the column
> So i try this code
> USE JMI
> GO
> sp_repldropcolumn @.source_object='ztest',@.column='dateDepart'
> GO
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'JMI_articles' because schema replication is performed.
> Server: Msg 5074, Level 16, State 1, Line 1
> The object 'DF__ztest__dateDepar__66D9612E' is dependent on column
> 'dateDepart'.
> Server: Msg 4922, Level 16, State 1, Line 1
> ALTER TABLE DROP COLUMN dateDepart failed because one or more objects
> access
> this column.
>
> It is possible to drop a column from a replication ?
>
>
>
>

Problem deleting publication

Hi All,

I have a problem, a user deleted some tables from a couple db's dealing
with replication. I now get this error on those db's.

The process could not execute 'sp_repldone/sp_replcounters on
servername

I have deleted one of the database's and neither are listed under
publications but they still show up under replication monitor.

Any ideas on how to delete them would be great. When I try I get

Error 208: Invalid object name 'sysarticles'
Invalid object name 'sysschemaarticles'
Could not use view or function 'sysextendedarticlesview' because of
binding errors.

TIA
DaveI figured it out, hope this helps someone.

I went into the distribution db and went thru every table and removed
any reference to the databases that were giving me problems. That got
rid of the ghost entries in the replication monitor folder. Oddly I
still had the red X's on the folders them selves but nothing under the
folders had X's and a refresh didnt make them go away. A
sp_MSload_replication_status did though.

Now just the database of the two that were needed still had the repl
hand icon on the database. The good old sp_removedbreplication got rid
of that.

Thanks,
Dave

problem creating trans. replication /sp_MShelp_replication_table

I'm using the wizard to create a trans. replication. When it tries to
retrieve the tables to publish
I get this error:
New Publication Wizard encountered one or more errors while retrieving
the list of articles on 'production'. The list of articles may not be
complete.
Invalid column name 'options'. (Microsoft SQL Server, Error: 207)
The details of the error refer to sp_MShelp_replication_table.
When I run that stored proc I get:
Msg 207, Level 16, State 1, Procedure sp_MShelp_replication_table, Line
59
Invalid column name 'options'.
What could be the issue?
-Phil
I found the problem. The database was originally a SQL2000 db that was
being replicated. It still had some tables like sysarticles. I
dropped those tables and it's fine now.
|||The reserved replication keywords are :
If your publishing table has column names reserved for merge processing, you
will not be able to generate an initial snapshot because of duplicate column
names. Reserved column names are:
a.. reason_code
b.. source_object
c.. reason_text
d.. Pubid
e.. conflict_type
f.. origin_datasource
g.. tablenick
h.. create_time
Option is a reserved sql keyword. Could you post the schema for this table
here?
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
"Phil Cruz" <philcruz@.gmail.com> wrote in message
news:1144171822.881370.203540@.z34g2000cwc.googlegr oups.com...
> I'm using the wizard to create a trans. replication. When it tries to
> retrieve the tables to publish
> I get this error:
> New Publication Wizard encountered one or more errors while retrieving
> the list of articles on 'production'. The list of articles may not be
> complete.
> Invalid column name 'options'. (Microsoft SQL Server, Error: 207)
> The details of the error refer to sp_MShelp_replication_table.
> When I run that stored proc I get:
> Msg 207, Level 16, State 1, Procedure sp_MShelp_replication_table, Line
> 59
> Invalid column name 'options'.
>
> What could be the issue?
> -Phil
>