Add new table to transactional replication with push subscriber

Hi there,

With SQL Server 2005 after adding a new table to replication, the entire snapshot is redone when initializing the snapshot agent. Ive read that with the pull subsciption there is a proc you can run to only snap the new object. Is there any way (besides creating a new publication) to stop the whole snapshot being redone for a push subscription?

Thanks

It seems there is no this kind of proc to only add snap new object, no matter for pull or push subscription. New added schema in publication will cause subscription to reinitialized , unless you manually add the new added objects into subscriber side and choose @.sync_type = 'none' to skip the initial snapshot.

Hope it will help.

Thanks

Yunjing

|||

Thanks for reply.

but surely this cant be right. in SS2000 only new objcts added were initialized. we have a database with over 40 GB replicated data and cant redo the whole snap every time another article is added.

|||A new snapshot is generated such that any new subscriber that is added can reference an up to date snapshot. The entire snapshot is NOT sent to the subscribers. Only the new objects are sent to each subscriber. So, you only get an incremental initialize when you add new articles to the publication.

Add "not for replication" without table rebuild

Hi,
Is there a way to add the "not for replication" option to
an identity field without rebuilding the entire table.
Thanks in advance.
try something like this
http://groups.google.com/groups?selm...&output=gplain
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"kb" <anonymous@.discussions.microsoft.com> wrote in message
news:483501c4a09d$12b8ff40$a301280a@.phx.gbl...
> Hi,
> Is there a way to add the "not for replication" option to
> an identity field without rebuilding the entire table.
> Thanks in advance.
|||Many thanks Hilary,
I needed this for a DB that is approaching 1TB right now
and a full table rebuild was not an option.
Thanks agin.

>--Original Message--
>try something like this
>http://groups.google.com/groups?selm...0TK2MSFTNGP12=
..phx.gbl&output=3Dgplain
>--=20
>Hilary Cotter
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>"kb" <anonymous@.discussions.microsoft.com> wrote in message
>news:483501c4a09d$12b8ff40$a301280a@.phx.gbl...
>
>.
>
|||Hilary Cotter wrote:
> try something like this
> http://groups.google.com/groups?selm...&output=gplain
>
Hilary,
Many thanks again for your help.
Everything worked as expected on my test system after turning on (not
for replication) as per the above article. However on the production
system after following exactly the same steps, replication still fails
with the 'cannot insert identity when identity_insert is off' problem.
I have checked that the table's identity column is 'identity yes (not
for replication'.
I'm sure I'm missing something really stupid here, as I am able to get
one system (SQL developer) to work whilst the production system (SQL
enterprise) fails.
Any pointers as to where to go from here would be appreciated.
TIA
Ken.