"Adam Patrick Cassidy" <apcassidy@aol.com> wrote in message
news:eoBB5en4GHA.1200@TK2MSFTNGP02.phx.gbl...
> I'm trying to add a column to my peer to peer replication. According to
> the help I've found:
>
> Adding Columns
> a.. To add a new column to a table and include that column in an existing
> publication, execute ALTER TABLE <Table> ADD <Column>. By default, the
> column is then replicated to all Subscribers. The column must allow NULL
> values or include a default constraint.
>
> b.. To add a new column to a table and not include that column in an
> existing publication, disable the replication of schema changes, and then
> execute ALTER TABLE <Table> ADD <Column>.
>
> c.. To include an existing column in an existing publication, use
> sp_articlecolumn (Transact-SQL), sp_mergearticlecolumn (Transact-SQL), or
> the Publication Properties - <Publication> dialog box.
> For more information, see How to: Define and Modify a Column Filter
> (Replication Transact-SQL Programming) and How to: Define and Modify a
> Column Filter (SQL Server Management Studio). This will require
> subscriptions to be reinitialized.
>
> d.. Adding an identity column to a published table is not supported,
> because it can result in non-convergence when the column is replicated to
> the Subscriber. The values in the identity column at the Publisher depend
> on the order in which the rows for the affected table are physically
> stored. The rows might be stored differently at the Subscriber; therefore
> the value for the identity column can be different for the same rows.
>
> However, while I am able to add the column to the publisher and it is
> replicated to the subscriber, I cannot update this column at the
> subscriber and have it replicate to the publisher. However when I update
> at the publisher it IS pushed to the subscriber.
>
> Outside of the new column, my updates bi-directionally work. Can someone
> tell me how I can get updates on newly added columns to be bi-directional?
>
> Thanks,
>
> Adam P. Cassidy
>

"Hilary Cotter" <hilary.cotter@gmail.com> wrote in message
news:%234SYrOq4GHA.1188@TK2MSFTNGP05.phx.gbl...
> Did you quiesce the system as outlined in this link?
>
> http://msdn2.microsoft.com/en-us/library/ms147385.aspx
>
> --
> 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
>
>
>
> "Adam Patrick Cassidy" <apcassidy@aol.com> wrote in message
> news:eoBB5en4GHA.1200@TK2MSFTNGP02.phx.gbl...
>> I'm trying to add a column to my peer to peer replication. According to
>> the help I've found:
>>
>> Adding Columns
>> a.. To add a new column to a table and include that column in an
>> existing publication, execute ALTER TABLE <Table> ADD <Column>. By
>> default, the column is then replicated to all Subscribers. The column
>> must allow NULL values or include a default constraint.
>>
>> b.. To add a new column to a table and not include that column in an
>> existing publication, disable the replication of schema changes, and then
>> execute ALTER TABLE <Table> ADD <Column>.
>>
>> c.. To include an existing column in an existing publication, use
>> sp_articlecolumn (Transact-SQL), sp_mergearticlecolumn (Transact-SQL), or
>> the Publication Properties - <Publication> dialog box.
>> For more information, see How to: Define and Modify a Column Filter
>> (Replication Transact-SQL Programming) and How to: Define and Modify a
>> Column Filter (SQL Server Management Studio). This will require
>> subscriptions to be reinitialized.
>>
>> d.. Adding an identity column to a published table is not supported,
>> because it can result in non-convergence when the column is replicated to
>> the Subscriber. The values in the identity column at the Publisher depend
>> on the order in which the rows for the affected table are physically
>> stored. The rows might be stored differently at the Subscriber; therefore
>> the value for the identity column can be different for the same rows.
>>
>> However, while I am able to add the column to the publisher and it is
>> replicated to the subscriber, I cannot update this column at the
>> subscriber and have it replicate to the publisher. However when I update
>> at the publisher it IS pushed to the subscriber.
>>
>> Outside of the new column, my updates bi-directionally work. Can someone
>> tell me how I can get updates on newly added columns to be
>> bi-directional?
>>
>> Thanks,
>>
>> Adam P. Cassidy
>>
>
>