Can I download a replica on day 1 and then on day 7 download the delta
to that replica?
Delta is the set of new records added to the server (from day 1 to day 7)
after i dowload the replica. Say on day1 I download a replica of 1000
records. Between day1 and day7, the server recieved 10 new records. On day 7,
I want to download
those 10 record only and add them to my replica. Is that possible by
default?
You cam assume there will be no collision bothways.
Thank you
http://groups-beta.google.com/group/...c41adc66b02687
Of course - transactional for one direction and bidirectional transactional
if not, as you are avoiding conflicts. Strictly speaking it is not the
record but a call to an insert sp that is replicated, but the end is the
same.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||My replica is merge replica
"Paul Ibison" wrote:
> Of course - transactional for one direction and bidirectional transactional
> if not, as you are avoiding conflicts. Strictly speaking it is not the
> record but a call to an insert sp that is replicated, but the end is the
> same.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||OK - changed records only are propagated in merge.
Paul
"Lottoman2000 NEWBE" <Lottoman2000NEWBE@.discussions.microsoft.com> wrote in
message news:6FA34369-67F7-4FD0-96ED-292F1E5E9BCA@.microsoft.com...[vbcol=seagreen]
> My replica is merge replica
> "Paul Ibison" wrote:
|||Can i keep downloading delta after sync my replica with the server.
assume no collision, I submit in 100 records that has changes and everything
goes through fine. The server has now 50 new and changed records (other than
mine) that were submited from another user. Can I download those record only?
Wont my replica expire after i sync and hence i will have to re-initialize
all the replica again?
Sorry for the late reply/comment!
Thanks
|||To be honest I don't entirely follow your scenario, but if you are concerned
about expiry, this is determined by the Publication Property illustrated on
the General Tab of the publication properties dialog box. It is 14 days by
default, so as long as your subscribers synchronize every 14 days, there'll
be no expiry.
HTH
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
No comments:
Post a Comment