Merge Replication with Restore Database

hi all,
We currently encounter a big trouble:
We have set up a model of synchronization from PDA to SQL Server
succesfully. Everything is OK until SQL Server database met a trouble
and needed to restore database. We restored a rather old database (1
week ago) and then so many erros appeared. Database that is in PDA
contains much newer data than on SQL Server. When we synchorize, it
appeared error 28549: "The row update or insert cannot be reapplied due
to an integrity violation".
I would like to ask whether there is a standard process for Merge
Replication in case of restoring old database ?
FYI: SQL Server 2K with SP3.
Very appreciated for any help.
KNC
This will work if the retention period of the publication is longer than the
age of the backup.
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"KNC" <khanh@.glassegg.com> wrote in message
news:1102943950.567639.151310@.z14g2000cwz.googlegr oups.com...
> hi all,
> We currently encounter a big trouble:
> We have set up a model of synchronization from PDA to SQL Server
> succesfully. Everything is OK until SQL Server database met a trouble
> and needed to restore database. We restored a rather old database (1
> week ago) and then so many erros appeared. Database that is in PDA
> contains much newer data than on SQL Server. When we synchorize, it
> appeared error 28549: "The row update or insert cannot be reapplied due
> to an integrity violation".
> I would like to ask whether there is a standard process for Merge
> Replication in case of restoring old database ?
> FYI: SQL Server 2K with SP3.
> Very appreciated for any help.
> KNC
>
|||hi Hilary,
You seems to misunderstand me, of course it still works. But it will
have trouble in following scenario:
- day 6, set up Merge Replication on SQL Server
- day 8, back up SQL Server database
- day 10, there is 1 new record 001 which is inserted into SQL
Server. Then it was synchronized with PDA, so PDA also contains this
new record 001.
- day 12, SQL Server database is corrupted, we restored from day 8.
Then record 001 is also inserted after database restored. When
synchronizing with PDA, it is conflicted with error 28549.
I would like to ask what is the standard process for Merge in case of
SQL server database is often restored.
Thanks much,
Khanh
Hilary Cotter wrote:
> This will work if the retention period of the publication is longer
than the[vbcol=seagreen]
> age of the backup.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> Now available for purchase at:
> http://www.nwsu.com/0974973602.html
> "KNC" <khanh@.glassegg.com> wrote in message
> news:1102943950.567639.151310@.z14g2000cwz.googlegr oups.com...
trouble[vbcol=seagreen]
(1[vbcol=seagreen]
due[vbcol=seagreen]

Merge Replication deployment model

In order to deploy the replication implementation along with the software that has been created,how to package the correct set of necessary assemblies along with our client to ensure that the software can function correctly?
While trying to include the SQL Server assemblies that we are using from the SDK directory, we get some internal security token errors.

Please also suggest what would be the recommended deployment model for stand-alone clients which are replicating between a local and remote server where the local doesn't include an install of the SQL management tools? (It will have express.)

What are the assembiles you are getting error on?

If your client is going to install SQL Express (with replication components) before your application will be installed, you will not have problems.

Also you could make SQL Express as a pre-requisite when you publish and that way the client will be able to install Express and then your application will not have any problems with dependencies.

merge replication and simple recovery model

Hi All,
Is it possible or okay for setting the publishing DB in a merge
replication setup to Simple recovery model instead of the current
Bulk-logged model?
Will this have an impact to the subscribers?
Thanks.
Aramid
Merge doesn't use the transaction log in the same way as transactional, but
even in this case it is a common misconception that FULL recovery mode is
necessary, so to answer your question 'Yes' - it has no effect as far as the
correct workings of replication are concerned.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)