Re: FE/BE Replication Question
- From: jacksonmacd <jackMACmacdo0nald@xxxxxxxxx>
- Date: Sun, 01 Jan 2006 00:48:36 GMT
You're welcome. Good luck with your project. Post back if you have any
additional questions.
On Sat, 31 Dec 2005 10:31:02 -0800, Debbie
<Debbie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>Thank you so much - I will definately investigate RWOP queries. I did read
>about them somewhat but I will look into them further. I can't thank you
>enough for helping with a subject that has very little documentation! Have a
>Happy New Year!
>Debbie
>
>"jacksonmacd" wrote:
>
>> On Sat, 31 Dec 2005 08:53:02 -0800, Debbie
>> <Debbie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>>
>> >All 3 of their servers are physically in the same location, in fact they are
>> >next to each other. The remote locations have 1 or 2 PCs that that users
>> >share. There are 3-4 users per location each with their own logon id and
>> >password.
>>
>> OK - since the servers are in the same physical location, then they
>> are on the same LAN, and direct synchronization is appropriate between
>> them.
>>
>> >
>> >The client had opted to use replication because they wanted each of the 12
>> >locations to view only their data. They sychronize at the end of each day.
>> >They do hide the design master and synchronize to a replica. There are 12
>> >copies of the database spread over the 3 servers.
>>
>> Have you considered using a single server, with a single database,
>> using Read With Owners Permission (RWOP) queries to restrict the
>> records that each user is allowed to see? It might be a simpler and
>> cleaner configuration than using multiple servers with partial
>> replication between them. RWOP queries are explained somewhat in the
>> Security FAQ -- see the website in my signature for a link if you
>> don't have it already.
>>
>>
>> >
>> >The central office wanted to report on the data for all locations. You
>> >mentioned they should not be doing replication. What are the risks in doing
>> >so? Thank you both SO MUCH for this valuable information.
>>
>> I think that I said doing direct synchronization over a WAN can lead
>> to database corruption. That's not your situation since the servers
>> are in a single physical location. Doing direct synchronization over a
>> WAN is problematic because both replicas involved in the sync need to
>> be opened simultaneously and WAN connectivity can be sporatic. A
>> dropped connection can corrupt the database.
>>
>>
>>
>> >Debbie
>> >
>> >"Debbie" wrote:
>> >
>> >> Hello all,
>> >> My client has an old Access application where all objects including tables
>> >> are in one database. They are also using replication whereas they have a
>> >> design master on the server and several locations have partial replicas which
>> >> are stored on the server, all clients are thin clients. They also are using
>> >> user level security. That all works fine.
>> >>
>> >> Now, I have re-written the application and in doing so have split the
>> >> database and continued to use user level security. That's all fine.
>> >> However, we are unsure about how to use replication in this design scenario.
>> >> The design parameters are:
>> >> - the design master and replicas are stored on the server.
>> >> - All the locations must have partial replicas containing only their data.
>> >>
>> >> I have the following questions:
>> >> 1. In this scenario, I can create partial replicas on the backend database.
>> >> However, should I create replicas for the front end database for each
>> >> location? Can you create a replica of a front end containing all objects
>> >> except tables? I have tried this and I got an error message. I think I need
>> >> to because the application is written in ADO and there are provider
>> >> statements with a hard coded path statement that points to the back end
>> >> database.
>> >> 2. Is there a way to synchronize a back end database from the front end?
>> >> In the old application since all object were in the same database, it wasn't
>> >> an issue.
>> >>
>> >> Thanks so much, I did download the Replication FAQ paper but nothing seems
>> >> to address this particular scenario. Any ideas are appreciated. Thanks so
>> >> much,
>> >> Debbie
>>
>> **********************
>> jackmacMACdonald@xxxxxxxxxxxxxx
>> remove uppercase letters for true email
>> http://www.geocities.com/jacksonmacd/ for info on MS Access security
>>
**********************
jackmacMACdonald@xxxxxxxxxxxxxx
remove uppercase letters for true email
http://www.geocities.com/jacksonmacd/ for info on MS Access security
.
- Next by Date: Re: Indirect Sync A97 - Replication Manager
- Next by thread: Re: Indirect Sync A97 - Replication Manager
- Index(es):
Relevant Pages
|
