Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
hankswart
Starting Member
5 Posts |
Posted - 2007-08-28 : 10:04:34
|
Hi,I will be attempting my first replication setup and was wondering if someone could supply me with some guidence. Here is what will be attempting to achieve.We have 5 very remote sites. Each containing a database called "PROD" with exactly the same schema (db structure). The schema has reference tables and data tables. The reference tables contain the same information at all sites. This is currently accomplished using manual export and import of csv files from/into the revantant reference tables. The data tables are only relevant to a specific site so this information is unique. The aim is to get a repository server at head office that contains all the information (reference and data tables) at each site into a single database for reporting purposes while keeping all reference tables syncronized between the repository and remote sites. How would I go about setting this up? Is it possible to have the reference tables bidirectional (keep all db's sync) and the data tables only replicate from the sites to the repository? So tha the data tables are not replicated to other sites?Thanks in advance... |
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-08-28 : 22:09:20
|
Take look at merge replication in books online. |
|
|
hankswart
Starting Member
5 Posts |
Posted - 2007-08-29 : 02:35:55
|
Thanks for the responce. Here is my solution so far: Central Publisher TopologyHead Office: DB Name: Repository Config: Distributor & Publisher Publishers: Reference Tables (Exchange Type = Bidirectional) Acticles will only be reference tables Data Tables (Exchange Type = Upload) Acticles will only be data tablesRemote Sites: DB Name: PROD Config: SubscriberWhat are your comments on the above solution? |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-08-30 : 01:39:17
|
Merge replication may add additional timestamp column in replicated table, ensure your app can handle that. |
|
|
|
|
|