Re: Merge Replication - Inventory Conflct Resolver
- From: "Hilary Cotter" <hilary.cotter@xxxxxxxxx>
- Date: Sun, 19 Mar 2006 18:50:17 -0500
David, I don't believe that merge replication is the way to solve this
problem. Conflict resolver is used to resolve conflicts. You might have a
case where subscriber 7 does not sells 20 items, and nothing is sold on the
publisher. This will not be detected as a conflict and hence any business
logic you implement in the resolver will not be enforced.
What you need to do is have some logic which will roll up sales as the end
of a sync.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"David Haas" <DavidHaas@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D8E24491-0640-418D-8D97-272816B94FBA@xxxxxxxxxxxxxxxx
Let me try and explain our planned setup. We will have servers at each of
our warehouse locations and use merge replication. One of these servers
is
our inventory server that keeps track of inventory on a bin by bin basis.
The information in this table basically consists of item, bin, qtyonhand.
I
can't figure out how to resolve conflicts on this table. We thought about
trying to get the delta as described but can't figure this out and I don't
think there is a direct way to do this. I know that people use
replication
on inventory data, through all my research cannot figure how they
accomplish
this.
"Hilary Cotter" wrote:
I question your logic here. You start off with an inventory level of 100.
Server A sells 20 units, server B sells 35 units. You wish a net result
globally to be 100-(20+35)=45. This is how you want your conflict
resolved,
with 45 on both sides.
The problem is unless you keep a record of the before on both sides you
can't really figure out the delta correctly. If you can do this, you do
the
math and have the resolver update the inventory on both sides.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"David Haas" <DavidHaas@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0FBB37F2-6D58-40B5-80D4-677B2F9A97F5@xxxxxxxxxxxxxxxx
We are trying to setup Merge replication on a table that contains
inventory
data and trying to create the custom conflict resolver through stored
procedures. I was wondering if anyone had any experience with this if
they
could share how they set up their conflict resolution for this.
From what I can tell when the tables are synched with each other and
there
is a conflict you only know what each servers current data is for that
record. For instance
Server A and Server B start with 100.
Server A has 2 transactions that reduce the qty by 10 each time
resulting
in
a qty of 80.
Server B has 3 transactions that reduce the qty by 5, 10, and 20
resulting
in a qty of 65.
How is this conflict resolved when this occurs. From what I have read
we
can retrieve the current publisher data and the current subscriber data
but
not the individual transactions. The resulting qty should be 45 since
once
server reduced it by 20 and the other by 35. But during the
resolutution
we
only see the qty of 80 from server A and qty of 65 from server B.
Any help is appreciated.
Thanks
.
- References:
- Re: Merge Replication - Inventory Conflct Resolver
- From: Hilary Cotter
- Re: Merge Replication - Inventory Conflct Resolver
- From: David Haas
- Re: Merge Replication - Inventory Conflct Resolver
- Prev by Date: Theory Question - Logreader Resiliency
- Next by Date: Re: Theory Question - Logreader Resiliency
- Previous by thread: Re: Merge Replication - Inventory Conflct Resolver
- Next by thread: Re: sql 2005 merge replication direction
- Index(es):
Relevant Pages
|