Arghhh!!!!!!!!!!!! Somehow I was assuming you would be doing a no-sync.
"Ronald Green" <zzzbla@gmail.com> wrote in message
news:1172412186.310429.11430@k78g2000cwa.googlegroups.com...
> Hi,
>
> I ran a little test, and it failed on delivering the snapshot because
> of that extra column on the subscriber side. So the moral of the story
> is to add the column in a post snapshot script which is not always the
> best idea (if you already have your schema deployed and something is
> dependant on this column), OR you can change the SYNC view on the
> publisher and add a blank column to it prior to running the snapshot
> agent.
>
> R. Green
>
>
> On Feb 25, 3:01 pm, "Hilary Cotter" <hilary.cot...@gmail.com> wrote:
>> It should work. This is the normal way of carrying out what you are
>> trying
>> to accomplish.
>>
>> --
>> Hilary Cotter
>>
>> 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 >>
>> "Ronald Green" <zzz...@gmail.com> wrote in message
>>
>> news:1172407317.380240.255030@t69g2000cwt.googlegroups.com...
>>
>>
>>
>> > Hi,
>>
>> > I've got a unidirectional transactional replication (on sql 2000) and
>> > I want to add a column to a table on the subscriber's side, the column
>> > allows nulls and is going to be updated on the subscriber.
>>
>> > I thought of creating the table, than adding the publication and when
>> > I add this specific article, tell it to truncate the table if it
>> > exists rather than to drop it.
>>
>> > Is there any flaw in this?
>>
>> > Thanks in advance,
>> > R. Green- Hide quoted text -
>>
>> - Show quoted text -
>
>