single DB, multiple publications

  • I have a single huge database, transactional replication is used.

    Currently all tables are under one publication, the problem is whenever there is a need to reinitialize the snapshot files on the remote distibutor, replication will take 3-3.5 hours to complete to to deliver snapshot files to the subscriber server. I'm thinking to create multiple publications so I can only reinitialize the group of affected tables. Also, since the DB was just deployed to production, there are times new tables are need to be created and need be added in publication. Like FirstBatchofPublication and SecondBatchOfPublication. Is this a good approach? Thanks in advance.

  • Yes, it is a good practice to have multiple publications if you have a large database. This will help you initialize snapshots.

    -Roy

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply