Let’s consider a scenario we have a database in which we have 3 tables 2 of them are already added in replication and we want to add a third table in publication.

This is more important when we have a larger database and we don’t want to reinitialize the replication.

To avoid complete snapshot of the Publisher database and to avoid re-initialization we need to make some changes in the existing replication. We need to set 2 properties to False as shown below

1. allow_anonymous
2. Immediate_sync

Execute below commands

Now add table T3 again from Publisher properties and press ok.

1. USE
2. GO
3. EXEC sp_changepublication @publication = ‘PubDB’,
4. @property = ‘allow_anonymous’,
5. @value = ‘false’
6. GO
7. USE
8. GO
9. EXEC sp_changepublication @publication = ‘PubDB’,
10. @property = ‘immediate_sync’,
11. @value = ‘false’
12. GO

Now add the new articles in existing publication

Now start Snapshot Agent

Now you can notice that it only creates a snapshot of one article instead of all articles, now start log reader agent if it’s in the stopped state.

Now as you can see a snapshot was generated but only for one article, so this article will be replicated to all subscriber without impacting existing replication.

Don’t forgot to execute below command at last to enable the disabled properties.

1. Use
2. GO
3. EXEC sp_changepublication @publication = ‘PubDB’,
4. @property = ‘allow_anonymous’ ,
5. @value = ‘True’
6. GO
7. Use
8. GO
9. EXEC sp_changepublication @publication = ‘PubDB’,
10. @property = ‘immediate_sync’ ,
11. @value = ‘True’
12. GO

Now you can verify the article on all your subscribers

If you want to know more about immediate sync command follow below link

1. Immediate_sync