Change Column lenght on a replicated database

I need to increase the a column in a replicated merge database. The
column is 100 char in lenght and I need to change it to 200. I have
read the "Schema Changes on Publication Databases". But it seems to
be a little confusing.
Thanks.
Alter table is possible in SQL Server 2005 but unfortunately this is not
possible in SQL Server 2000. You could drop and readd the subscription, or
you could solve it in a roundabout way: add a new column with the new
datatype (sp_repladdcolumn), do an update on the table to populate the
column, then drop the column (sp_repldropcolumn). Do this again to create
the column having the same original name.
HTH,
Paul Ibison
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message news:<#Q7NK#KrEHA.2588@.TK2MSFTNGP12.phx.gbl>...
> Alter table is possible in SQL Server 2005 but unfortunately this is not
> possible in SQL Server 2000. You could drop and readd the subscription, or
> you could solve it in a roundabout way: add a new column with the new
> datatype (sp_repladdcolumn), do an update on the table to populate the
> column, then drop the column (sp_repldropcolumn). Do this again to create
> the column having the same original name.
> HTH,
> Paul Ibison
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
Thank you that's what I thought. Unfortunally, I have SQL 2000 and it
seems there are a lot of steps for something so simple. Maybe I should
just stop replication make the changes, delete the replica and do
replication again.
Same amount of work I guess
|||This has caused us a lot of heartache also... Such a simple thing! Once this
stuff is in production it can be a nightmare & unnecessary risk to change
columns
"xkravenx" <scubamike@.gmail.com> wrote in message
news:596eda8b.0410080740.76ee0786@.posting.google.c om...
> "Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:<#Q7NK#KrEHA.2588@.TK2MSFTNGP12.phx.gbl>...[vbcol=seagreen]
or[vbcol=seagreen]
create
>
> Thank you that's what I thought. Unfortunally, I have SQL 2000 and it
> seems there are a lot of steps for something so simple. Maybe I should
> just stop replication make the changes, delete the replica and do
> replication again.
> Same amount of work I guess