|
Home > Archive > MS SQLCE > March 2006 > Replication Concurrency
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Replication Concurrency
|
|
| Shaun Camilleri 2006-03-23, 1:31 pm |
| Hi all,
I have recently started to test out replciation between SQL and SQLCE. It
works ok, but on some more test I dicovered that when I synchronize, the
Device database always accepts SQL data (when that is changed), thus
overwriting any data that was entered in the Device.
So, is it possible for me to get any form of Concurrency Exception or any
other way to know data changed on server side?
| |
| Darren Shaffer 2006-03-23, 8:34 pm |
| help me understand this better - you are saying that a record is changing on
the
server and you are seeing the change on device? that is intentional unless
you
mark your subscription as upload only.
--
Darren Shaffer
..NET Compact Framework MVP
Principal Architect
Connected Innovation
www.connectedinnovation.com
"Shaun Camilleri" <shaun@holistic.com.mt.nospam> wrote in message
news:unQ3lbpTGHA.1160@TK2MSFTNGP09.phx.gbl...
> Hi all,
> I have recently started to test out replciation between SQL and SQLCE. It
> works ok, but on some more test I dicovered that when I synchronize, the
> Device database always accepts SQL data (when that is changed), thus
> overwriting any data that was entered in the Device.
>
> So, is it possible for me to get any form of Concurrency Exception or any
> other way to know data changed on server side?
>
| |
| Evan Camilleri 2006-03-24, 7:38 am |
| What Shaun meant was:::
Assume the following 3 situations
1 = On record X, if there is a change on the Device and not on Server then
it is uploaded on Server. = OK
2 = On record X, if there is a change on the Server and not on Device then
it is uploaded on Device. = OK
3 = On record X, if there is a change on the Server and on Device then the
one on the Server wins. = NOT OK
In case 3 the problem is that we want to receive some kind of event to tell
me that there is a replication conflict.
Evan
"Darren Shaffer" < darrenshaffer@discus
sions.microsoft.com> wrote in message
news:ehCzSvtTGHA.1728@TK2MSFTNGP11.phx.gbl...
> help me understand this better - you are saying that a record is changing
> on the
> server and you are seeing the change on device? that is intentional
> unless you
> mark your subscription as upload only.
> --
> Darren Shaffer
> .NET Compact Framework MVP
> Principal Architect
> Connected Innovation
> www.connectedinnovation.com
>
> "Shaun Camilleri" <shaun@holistic.com.mt.nospam> wrote in message
> news:unQ3lbpTGHA.1160@TK2MSFTNGP09.phx.gbl...
>
>
| |
| Darren Shaffer 2006-03-25, 11:28 am |
| you can use Replication Monitor on the server to view conflicts and
setup alerts and rules for handling them. unlike RDA which uses a
modified form of optimistic concurrency which says the records pushed
to the server will always overwrite the server side record, merge
replication
is more advanced than what you have described in scenario 3 below -
the server doesn't always win - see:
http://msdn.microsoft.com/library/d...ltypes_30z7.asp
--
Darren Shaffer
..NET Compact Framework MVP
Principal Architect
Connected Innovation
www.connectedinnovation.com
"Evan Camilleri" <e70mt@yahoo.co.uk.nospam> wrote in message
news:%23FcqD0yTGHA.4960@TK2MSFTNGP12.phx.gbl...
> What Shaun meant was:::
>
> Assume the following 3 situations
>
> 1 = On record X, if there is a change on the Device and not on Server then
> it is uploaded on Server. = OK
>
> 2 = On record X, if there is a change on the Server and not on Device then
> it is uploaded on Device. = OK
>
> 3 = On record X, if there is a change on the Server and on Device then the
> one on the Server wins. = NOT OK
>
> In case 3 the problem is that we want to receive some kind of event to
> tell me that there is a replication conflict.
>
> Evan
>
>
>
> "Darren Shaffer" < darrenshaffer@discus
sions.microsoft.com> wrote in
> message news:ehCzSvtTGHA.1728@TK2MSFTNGP11.phx.gbl...
>
>
|
|
|
|
|