another sp_repladdcolumn option question

Syntax
sp_repladdcolumn [ @.source_object = ] 'source_object'
, [ @.column = ] 'column' ]
[ , [ @.typetext = ] 'typetext' ]
[ , [ @.publication_to_add = ] 'publication_to_add' ]
[ , [ @.schema_change_script = ] 'schema_change_script' ]
[ , [ @.force_invalidate_snapshot = ] force_invalidate_snapshot ]
[ , [ @.force_reinit_subscription = ] force_reinit_subscription ]
I need clarification on the last 2 options here. I know it seems the name
says it all but its the ripple effect I'm not clear on... for example, if I
choose to invalidate the snapshot what happens? .. how is the merge repl
subscriber effected? and, for example, if I choose to reinitialize, when
does it happen and can I use the option to bring subscriber data back to the
publisher first? (like you can when using the GUI)
I have some basic assumptions about these last 2 options but I need to be
very clear on the why and when to use them? example scenarios would be very
helpful.
any info is appreciated. thanks.
basically there are some changes you can make to a publication which will
force a reinitialization, or invalidate the existing snapshot for new
subscribers.
If you make a change and set @.force_invalidate_snapshot to 0, you should
(but don't) get an error message which basically tells you the existing
snapshot will be invalidated.
If you set this to 1, you won't get this error message, as the proc assumes
you know your existing snapshot will be invalidated.
Same type of logic applies for the @.force_reinit_subscription parameter.
Setting it to a value of 0 will raise an error if the change is going to
break your publication/subscription and you have to re-initialize. Setting
it to 1 will assume you know what you are doing, no error is raised and the
publication/subscription is marked for reinitialization.
A bug will not raise the error. I reported this to Microsoft and a bug was
filed.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"djc" <noone@.nowhere.com> wrote in message
news:ufdiVedXEHA.2840@.TK2MSFTNGP11.phx.gbl...
> Syntax
> sp_repladdcolumn [ @.source_object = ] 'source_object'
> , [ @.column = ] 'column' ]
> [ , [ @.typetext = ] 'typetext' ]
> [ , [ @.publication_to_add = ] 'publication_to_add' ]
> [ , [ @.schema_change_script = ] 'schema_change_script' ]
> [ , [ @.force_invalidate_snapshot = ] force_invalidate_snapshot ]
> [ , [ @.force_reinit_subscription = ] force_reinit_subscription ]
> I need clarification on the last 2 options here. I know it seems the name
> says it all but its the ripple effect I'm not clear on... for example, if
I
> choose to invalidate the snapshot what happens? .. how is the merge repl
> subscriber effected? and, for example, if I choose to reinitialize, when
> does it happen and can I use the option to bring subscriber data back to
the
> publisher first? (like you can when using the GUI)
> I have some basic assumptions about these last 2 options but I need to be
> very clear on the why and when to use them? example scenarios would be
very
> helpful.
> any info is appreciated. thanks.
>
|||basically there are some changes you can make to a publication which will
force a reinitialization, or invalidate the existing snapshot for new
subscribers.
If you make a change and set @.force_invalidate_snapshot to 0, you should
(but don't) get an error message which basically tells you the existing
snapshot will be invalidated.
If you set this to 1, you won't get this error message, as the proc assumes
you know your existing snapshot will be invalidated.
Same type of logic applies for the @.force_reinit_subscription parameter.
Setting it to a value of 0 will raise an error if the change is going to
break your publication/subscription and you have to re-initialize. Setting
it to 1 will assume you know what you are doing, no error is raised and the
publication/subscription is marked for reinitialization.
A bug will not raise the error. I reported this to Microsoft and a bug was
filed.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"djc" <noone@.nowhere.com> wrote in message
news:ufdiVedXEHA.2840@.TK2MSFTNGP11.phx.gbl...
> Syntax
> sp_repladdcolumn [ @.source_object = ] 'source_object'
> , [ @.column = ] 'column' ]
> [ , [ @.typetext = ] 'typetext' ]
> [ , [ @.publication_to_add = ] 'publication_to_add' ]
> [ , [ @.schema_change_script = ] 'schema_change_script' ]
> [ , [ @.force_invalidate_snapshot = ] force_invalidate_snapshot ]
> [ , [ @.force_reinit_subscription = ] force_reinit_subscription ]
> I need clarification on the last 2 options here. I know it seems the name
> says it all but its the ripple effect I'm not clear on... for example, if
I
> choose to invalidate the snapshot what happens? .. how is the merge repl
> subscriber effected? and, for example, if I choose to reinitialize, when
> does it happen and can I use the option to bring subscriber data back to
the
> publisher first? (like you can when using the GUI)
> I have some basic assumptions about these last 2 options but I need to be
> very clear on the why and when to use them? example scenarios would be
very
> helpful.
> any info is appreciated. thanks.
>