Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Replication and Split Db

Status
Not open for further replies.

MajP

Technical User
Aug 27, 2005
9,382
US
Current I have a replicated db with each user have a Front end and a replicated backend. This allows the user when disconnected to work on their database replicas, but more importantly it allows offsite users to synchronize through a vpn. The VPN is to slow for them to connect directly to the backend (master) on our server. This works fine (actually better than I would have thought).

So my question is can I have users in the office point their front ends directly to the db master on the local server and not use a local replica on their machine? They then would never have to worry about synchronizing. The offsite user would then use replicas and synchronize like they currently do. This reduces the amount of synchronization and for the people in the office it makes keeping data current a lot easier. I ran a test on my machine where I was linked directly to the Master and still was able to synchronize from another machine (I did not think that would work, but it did). Is this a good idea or bad idea? Anyone have experience in this area?
 
I agree that local users should point their FE directly to the master BE.

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886
 
Thanks PHV. So I will plan for local users to link directly to the master and remote users to use local replicas and synchronization.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top