Do not worry about Msmerge_history being cleanup, since this table is bound to be cleanup anyway, automatically by way of system clean up scheduled task,which is autocreated during replication setup.

Just...

You can increase the # of attempts it can try to reconnect when it fails to connect. Agent will keep on retrying till it reached the # of attempts.

This can...

Yes.

You can avoid, by restoring a copy of the database at the subscriber. while setting up snapshop there is an option which will prompt to do this.

HTH

rangark

Hi,

In your case, looks like replication setup process was NOT completed successfully.

Drop the subscription/publication and try to recreate the replication process again. (Need to identify data which is more...

There is a system job to clean up subscription if inactive which could have cleaned up this. You can trace this part of the job history .

There is no short-cut...

You should use 'sa' login to setup the replication. don't try use any other login for the replication setup process

rangark

1. You could register the server with a name (named pipes) and could easily setup the replication

2. In the scenario you have explanied, you could do a merge replication of...

Another simple method to handle this  is to reseed the identity values, using DBCC CHECKIDENT. 

These types of situation could happen when a transactions which begin did not rollback completely (programming...

The cleanup is done by "expired subscirption cleanup" job, which is not dependent on the rention period. The sp sp_expired_publication_cleanup is deleting the subcription,irrespective of the data is in queue or...

I had responded on the same question when raised by another forum member.

We have been using the following method which we found simple and reliable

1. Create the table at subscriber...

check out the following

1. Some business rules part of the stored procedures where the deletes are happening, requires review

2. As a workaround try restoring a latest copy of the replicated database...

You can see part of Table -design mode.

Hi,

Check whether you have unchecked the foriegn key relationship "Enforce Relationship on Replication" across all the replicated databases across these servers. Checking this could lead to the problem you have...

First Suggestion

On the SQL Server Client , register the server used named pipes -server name instead of using IP to connect to the server. After this ,use the wizard to...

1.You should use name pipes (SqL Server Registration - Client setup) for setting up the replication process

2. If you don't see the required values. You can go and update the...