How can implement these simple scenario
- From: Lottoman2000 NEWBE <Lottoman2000 NEWBE@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 11 Apr 2005 10:03:01 -0700
Hello All,
I admit I am new to the replication spectrum, all my experience is basically
reading.
If you know of a book or site that has all the details please let me know.
These scenarios occur in the application that I am about to develop
Scenario #1
Client X wants specific data be download to use/modify offline. The data
changes will then be merged back with the server. As I see now, and I could
be totally wrong so please correct me, that can be done through stored
procedures on the server. I mean the client can call a stored procedure on
the server (publisher) with the specified parameters (say all the records
from Table= "SALES" Where City = "NEW YORK"). The stored procedure generates
the replica (must be pull type) and then the client subscribes to replica,
download locally (pull, on demand) and disconnect. Note download and upload
(for synchronization) must be Client-triggered i.e. on demand.
Is there such thing as Client Initiated (pull) replicas? if yes how can we
do it?
Scenario #2:
Client X schedule to synchronize. how does the data get uploaded to the
server? do I trigger the merge manager? I want to have control when a merge
can take place
Scenario #3
Client X schedule a sync. and shuts down and the user goes on 3 day vacation.
I know how collision detection woks. In our model the server always wins in
collisions.
How would client X know of a conflict next time it logs in?
How much data is kept in the System tables on the server about the
collisions?
Info about the pending CRUD transactions.
How do I poll the merge agent on the client to know how many transaction
there pending sync with the server?.
How do I set a threshold to force CLIENT X to sync every 100 or so CRUD
transaction.
Is there an merge agent API to pull out this info. or where can I get the
info?
Collinsions or related multi-Record and rollback.
How do I roll back on multi record merge?. Say Record A and B can both take
place or none. so if A is ok in Table-A and B has collided in Table-B then
roll back both. If A collides in Table-A then abort operation.
I still have few more questions that are dependents on those. So will wait
till I hear from you first.
Thank you for the help.
Canada
.
- Follow-Ups:
- Re: How can implement these simple scenario
- From: Hilary Cotter
- Re: How can implement these simple scenario
- From: Paul Ibison
- Re: How can implement these simple scenario
- Prev by Date: Re: Best way to copy database
- Next by Date: Help with these scenarios
- Previous by thread: Backup Strategy
- Next by thread: Re: How can implement these simple scenario
- Index(es):
Relevant Pages
|