I have two database servers:
1. DB1
2. DB2
Both are SQL Server 2012
. DB1
– is a production server. DB2
– is a server which is used only for reporting. There is a transactional replication, which replicate data between DB1
(publisher) and DB2
(subscriber and distributor).
Recently database size has grown and if I need to add or delete any object it takes too much time to make a snapshot, send it to Distributor
and apply all changes to Subscriber
. Now it takes 3+ hours which is not reasonable for me.
So I wonder if I could configure multiple publications – one for the biggest tables which are not changed to often and one for all other objects.
Does it make sense?
What do you think about any cons of this solution?
Maybe you could provide any other solutions for this case?
Thank you.
Best Answer
Make sure both of these settings for your publication is set to False which is the default. It these are set to FALSE and you DO NOT reinitialize your subscription snapshot should only be generated for new articles.
If you are changing any portieres of the article you have to reinitialize and recreate full snapshot.
My personal preference is to group articles into multiple publications. That way even you have to reinitialize subscriptions and generate new snapshot you can run multiple jobs at the same time. You will need to make a choice if you want shared or individual (per publication) distribution agents.