By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,843 Members | 2,324 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,843 IT Pros & Developers. It's quick & easy.

Replication - Single Publication versus Multiple Publications

P: n/a
We are looking to implement merge replication on our global databases.
The decision that we must make is whether to place all of the tables in
a single publication, to create publications that are grouped by system
modules, or to create a publication for each table. What I am looking
for is best practices or recommendations based on your experience as
far as what approach to take on this. The database contains
approximately 300 tables. Each approach offers advantages and
disadvantages. The biggest disadvantage on the single publication is
flexibility. The biggest disadvantage on each table being a
publication is maintainability. Is there a scalability issue with
either of these approaches? Do all records that have foreign key
constraints have to be in the same publication?
Any guidance is very much appreciated.

Thanks,
Kent

Jul 23 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.