Set subscriber to other status ?

Hi There

My problem is that a while ago i posted a question here reagrding changing remote distributors without having to reinitialize subscriptions becasuse alot of data was involved and creating and applying the snapshot would require too much downtime.

The solution provided (briefly) involved using the option that states subscriber already has meta data and data option when creating the subscription.

This worked great as i unsured that no transactions were happening so when i changed distributors it just carried on replicating without a new snapshot needed because my subscriber had the data etc.

Not i have a nasty problem.
I am unable to add columns or articles to the publication, i know exactly why, because i stipulated that the subscriber had the meta dat etc.

I need to know is there a way i can change this ?
All my other publications work 100% if i add columns or articles the changes are automatically applied to the subscribers.

With this publication i know how to make it work but it is a long process.
If i make changes to the publciation, the distribution agent fails because changes are not applied to the subscriber automatically , but the distribution agents expects the changes i have made to be there , for example it will fail on a column not being present at the subscriber , a new column i just added that is.

I have looked at the system replication sp's , i am sure there must be a way to change the subscription properties so that in future changes are automatically applied to the subsciber , that is the subscriber no longer has the meta data when new columns or tables are added.

Does anyone know how i can achieve this, as i said before because of the amount of data involved i really want to avoid reinitializing the subscription requiring a new snapshot.

Thanx

[1830 byte] By [SeanDL] at [2008-2-28]
# 1
SeanDL,

I tried to repro the issue you have by following your steps above using tran read-only publication with push agent using replication support only option, but could not repro it. In my case, the new article or add/drop column was immediately replicated to subscriber.

Can you provide more information about your environment so we can better under the problem you have?

1. What kind of publication you're using? Tran (updatable?), merge? Do you have DDL replication turned on in your publication?
2. If possible, script out the replication setup on your environment and attach it to this thread, plus the table schema, the DML statement you used to make changes
3. Exactly what step did you perform to run into your current situation? Was the replication support only option is not turned on initially?
Thanks,

Zhiqiang

Zhiqiang at 2007-9-9 > top of Msdn Tech,SQL Server,SQL Server Replication...

SQL Server

Site Classified