You can do this using just about any method of replication. Transactional as well as merge will work in both a connected and disconnected manner, as long as you do not have conflicts occuring between sites. The number of transactions does not matter either. As long as you are partitioning the tables based on the site, then you can handle moving the rows to where they belong. The biggest challenge is going to be in desiging your paritions such that your data is logically split. If you are moving data via static partitions, transactional would be a better choice. If you are dynamically splitting the data or you are partitioning multiple tables based upon a "master" table, then merge would be a better choice.
For More Information
- Dozens more answers to tough SQL Server questions from Michael Hotek are available here.
- The Best Microsoft SQL Server Web Links: tips, tutorials, scripts, and more.
- The Best SQL Web Links
- Have a SQL Server tip to offer your fellow DBAs and developers? The best tips submitted will receive a cool prize. Submit your tip today!
- Ask your technical SQL Server questions -- or help out your peers by answering them -- in our live discussion forums.
- Ask the Experts yourself: Our SQL, database design, SQL Server, DB2, object-oriented and data warehousing gurus are waiting to answer your toughest questions.
Dig Deeper on SQL Server Replication
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.