Hi, we are using merge replication from our server (SQL Server 2005) to what
will soon be hundreds of subscribers. The subscribers are actually from a
Windows app that uses a SQLCE database. The client app is able to insert and
update records that are then merged up to the server. ...

I've noticed lately that I'm getting a few 28039 & 28040 Errors. The
replication still seems to work though i.e. changes are synchronised.
Any idea what the cause of these errors may be?
Cheers.

I have two servers: Publisher, Subscriber
Between them there is transactional replication
On both servers the recovery model is simple.
If the publisher goes down and the database has been corrupted. and I need

From some investigations i've made it seems that transaction log for
replication slowing performance.
But on simple recovery model the transaction log used for transactional
replication slowing performance less then recovery model full.

is there any procedure or query to find out the transactions which are not
yet replicated?
RegarDs,
Jacx

Maybe I'm being dense, but I can't figure out how to change the XXX in
"Waiting xxx  second(s) before polling for further changes." in my merge
replication on my SQL 2005 Servers.
When looking it up online I find references to pollinginterval, but the only

Hi - When synchronizing, the following conflict occurred:
   INSERT statement conflicted with COLUMN FOREIGN KEY constraint
'FK_ContraintName'. The conflict occurred in database 'DatabaseName', table
'TableName', column 'PrimaryKeyCol'.

SQL 2005 (SP1, +2153)
Why does creating a Snapshot publication (with only stored procedures and
functions) set the Transactional option on the Publisher?
My intent is to create two separate publications (one Merge, the other

After losing my publishing server, I re-built on a new server.
The databases had replication remnants so I ran cleanup scripts
(Replication system Objects, indexes and rowguids)
I then re-built replication

I am attempting to create a merge publication from  SQL 2005 to SQL
2000.  I am checking the 2005 & 2000 boxes for compatability, but
receive this message.
Publication 'edi' cannot be added to database 'EDI', because a

We are configuring merge replication with web synchronization and I was
curious to know the extent of how the snapshot share is used.  Specifically,
does SQL Server only store the schema information here and is data ever
stored there for any period of time.  My reading indicates ...

I have an off-site server that received log shipments every 30 minutes.  It's
been working fine for years.
However, the off-site server lost network connectivity for a few days.  This
was more time than was permitted by the out-of-sync threshold.

All,
I'm looking for advice on the best practive for replicating data to a
different server so that during server failure I can switch without any
major delay. Any advice or clarification would be greatly appreciated.

We have implemented SSL Encrytion on one of our SQL Server 2000 box to
encrypt DTS Packages.  I'm having a hard time trying to find anything about
encryption during replication.  I did find that you can configure encrytion
in the Replication Merge Agent in SQL 2005.  Does anyone ...

1) Can you use the Default Interactive Resolver with SQL Express and Merge
Replication ?
2) Has anyone successfully done this?
My setup is Windows XP Laptop with SQL Express, Windows Server 2003 with SQL