Replication Configuration?

Our website and sql database are hosted away from our offices and is updated via the web by customers and by us in our offices. However due to our slow internet connection we would like to bring a replication server into our office and have the two databases talk to each other when a change occurs.(Customers updating the public database and us update a local one).

I have seen sites mention circular replication is troublesome and may not work, is this the case or is it just a matter of correct configuration?

Any advice, tips etc would be appreciated.

Thanks

John

I guess u need a Transactional replication configured between the two server.

Two scenario u can have

1. Central publishers and many(as many as u wish) read only subscriber

2. Other case in which subscribers also get updated Immediate updating subscribers.

I guess u have a scenario where in both the server will get updated. u can go for transactional replication with immediate updating subscribers.

I see no issues in this and ofcourse correct configuration is must for anything u do with SQL Server.

|||

Also i have one more quick question..how frequent is update on the both the server?

if both server are frequently updated u should consider using merge replication instead of transactional replication with immediate updating subscription as immediate updating subscription is useful for only occasional changes on the subscribers.

|||

I posted this on a different thread, but I think it applys to you as well.

Here is a direct quote from BOL http://msdn2.microsoft.com/en-us/library/ms152570.aspx

The following types of replication and replication options allow you to make changes at a Subscriber and have those changes flow to the Publisher:

Type of replication

Use when…

Merge replication

There are a large number of Subscribers.

Data is replicated to mobile users.

Replicated data is frequently updated at the Subscriber.

Data filtering is needed so that Subscribers receive different partitions of data.