Push subscription: "schema and data"

If I make a database-structure change on the Publisher, will the structure
change replicate to the Subscriber (and update the structure there) ?
When pushing a new subscription, the wizard prompts if you would like to
push schema and data. Does 'schema' mean ... the database structure?
Thank you,
Bob
Use the sp_repladcolumn and sp_repldropcolumn stored procedures to replicate
schema changes for existing publications with subscriptions.
When you get the message - push schema and data, the schema does refer to
the table (and other objects) creation scripts - or as you put it database
structure.
"Robert A. DiFrancesco" <bob.difrancesco@.comcash.com> wrote in message
news:eHTYxKGaEHA.3708@.TK2MSFTNGP10.phx.gbl...
> If I make a database-structure change on the Publisher, will the structure
> change replicate to the Subscriber (and update the structure there) ?
> When pushing a new subscription, the wizard prompts if you would like to
> push schema and data. Does 'schema' mean ... the database structure?
> Thank you,
> Bob
>
|||Thank you very much.
Just so that I am very clear, if I had made a manual change to the database
(not using the sp's you have pointed out) and I push out the subscription
without the database and schema because there is an existing database, then
the structure change would NOT replicate. Is this correct?
Thank you.
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:OTqXliGaEHA.2516@.TK2MSFTNGP10.phx.gbl...
> Use the sp_repladcolumn and sp_repldropcolumn stored procedures to
replicate[vbcol=seagreen]
> schema changes for existing publications with subscriptions.
> When you get the message - push schema and data, the schema does refer to
> the table (and other objects) creation scripts - or as you put it database
> structure.
> "Robert A. DiFrancesco" <bob.difrancesco@.comcash.com> wrote in message
> news:eHTYxKGaEHA.3708@.TK2MSFTNGP10.phx.gbl...
structure
>
|||its hard to tell what you mean.
If you make a schema change, and then create a publication and push it to a
subscription, yet the subscribers will get the schema change.
If you attempt to make a schema change to an existing publication and
subscription(s) you will be prevented from doing with an error message like
'This table is published for replication'.
The only way to do this is using the above mentioned replication stored
procedures.
"Robert A. DiFrancesco" <bob.difrancesco@.comcash.com> wrote in message
news:ei7Tb4GaEHA.2488@.tk2msftngp13.phx.gbl...
> Thank you very much.
> Just so that I am very clear, if I had made a manual change to the
database
> (not using the sp's you have pointed out) and I push out the subscription
> without the database and schema because there is an existing database,
then[vbcol=seagreen]
> the structure change would NOT replicate. Is this correct?
> Thank you.
>
>
> "Hilary Cotter" <hilaryk@.att.net> wrote in message
> news:OTqXliGaEHA.2516@.TK2MSFTNGP10.phx.gbl...
> replicate
to[vbcol=seagreen]
database[vbcol=seagreen]
> structure
to
>
|||The situation is this:
I had to delete my publication in order to make a database structure change
at the publisher ( I did get the error you mention).
I then re-created my publication and pushed a new subscription to my
subscriber. But I did not "check" the box to send schema and data.
So my subscriber indeed does not have the database change. This appears to
be my problem.
In the future it would appear I have three options:
1) update the databases at both the publisher and the subscriber.
Indicate that the schema and data do not have to be sent when pushing a new
subscription.
2) update the publisher and push the new database structure along with
the data, with the new subscription (which may take a while over the
Internet)
3) Just use those stored procedures and I am done!
Would you agree? Looks like I'll take curtain number 3...
thank you very much for your time and patience,
bob.
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:%23gb6XBHaEHA.1488@.TK2MSFTNGP09.phx.gbl...
> its hard to tell what you mean.
> If you make a schema change, and then create a publication and push it to
a
> subscription, yet the subscribers will get the schema change.
> If you attempt to make a schema change to an existing publication and
> subscription(s) you will be prevented from doing with an error message
like[vbcol=seagreen]
> 'This table is published for replication'.
> The only way to do this is using the above mentioned replication stored
> procedures.
> "Robert A. DiFrancesco" <bob.difrancesco@.comcash.com> wrote in message
> news:ei7Tb4GaEHA.2488@.tk2msftngp13.phx.gbl...
> database
subscription[vbcol=seagreen]
> then
> to
> database
?[vbcol=seagreen]
like[vbcol=seagreen]
> to
structure?
>
|||yes, I would try option 3.
It seems to me that in the past #3 has bitten me in certain situation like
when you have filters, but I have been able to repro it.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Robert A. DiFrancesco" <bob.difrancesco@.comcash.com> wrote in message
news:OLSBwMHaEHA.1448@.TK2MSFTNGP12.phx.gbl...
> The situation is this:
> I had to delete my publication in order to make a database structure
change
> at the publisher ( I did get the error you mention).
> I then re-created my publication and pushed a new subscription to my
> subscriber. But I did not "check" the box to send schema and data.
> So my subscriber indeed does not have the database change. This appears
to
> be my problem.
> In the future it would appear I have three options:
> 1) update the databases at both the publisher and the subscriber.
> Indicate that the schema and data do not have to be sent when pushing a
new[vbcol=seagreen]
> subscription.
> 2) update the publisher and push the new database structure along with
> the data, with the new subscription (which may take a while over the
> Internet)
> 3) Just use those stored procedures and I am done!
> Would you agree? Looks like I'll take curtain number 3...
> thank you very much for your time and patience,
> bob.
>
>
> "Hilary Cotter" <hilaryk@.att.net> wrote in message
> news:%23gb6XBHaEHA.1488@.TK2MSFTNGP09.phx.gbl...
to[vbcol=seagreen]
> a
> like
> subscription
refer[vbcol=seagreen]
message[vbcol=seagreen]
there)
> ?
> like
> structure?
>