I am using merge pull replication with 10 subscribers and 1 publisher all
connected with a VPN. They are not in a trusted domain so I am using SQL
Authentication. The 10 subscribers are not trusted to see each others data so
the snapshot folders

I have a publication, with 2 subscriptions, that is currently working
fine.  I added a new subscription to the publication, run the snapshot
agent & when the subscription/dist agent runs, I get the message
"""The initial snapshot for publication 'publication name here' is not

i know to add a column to a table i have to use the sp_repladdcolum.
My issue is on the publisher a column is defined as INT and allows
nulls. the two subscribers have the same column set as int and allow
nulls is not checked with the default value set as zero.

We have lost  the common distribution cleanup/history jobs in an instance of
SQL2005 (Clustered Enterprise).  Trying to go back to backups to find copies
has not proven fruitful, and we don't have a script  saved.  Is it possible
to script  out these jobs from a nother ...

I have a problem and I need help.
I get this error in my sql server replication:
"Transaction (Process ID %d) was deadlocked on %.*ls resources with another
process and has been chosen as the deadlock victim. Rerun the transaction".

i have used:
delete from msmerge_tombstone
where tablenick in (select nickname from sysmergearticles where
tablenick=nickname and name='utaudit') and

I have a problem with my transactional replication. I get a deadlok between
distribution agent and clenup agent. How can I solve this problem??.
Thanks.

My environment
ServerA -- TableA
ServerB -- TableB (same schema as ServerA.TableA)
Now whenever a transaction happens in TableA I want it to be replicated

I want to create a new database for reporting and the data will be
replicated from our OLTP database. Is there any benefit if i use the the same
instance as where the OLTP database is or should i create a new instance for
the reporting database?   I  only have one machine ...

My application uses *= and =* as outter join, so, I had to create my db in
SQL 2000 Compatible Mode, in order to run this application.
But a question: The merge replication should work fine on Sql2005 using
Sql2000 Compatible mode ?

I am attempting to initialize a pull merge subscription using the following
code:
---
ServerConnection sc = new ServerConnection(connReplicate);

I am in desparate need of help, or shot, one of the  two.
I am at the finishing line of a project and now am a week late because of a replication error that has me totally stumped.
I have set up replication between MSDE SP4 on local PC and MSDE SP4 on web server, on my Vista ...

I'm trying to create a publication on a Windows 2003 server running SQL
server 2005.  I'm getting the following message when I try to create a
disctributor:
SQL Server is unable to connect to server '123abc'

I have a SQL Server 2000 database that I have set up with SQL Server 2000
merge replication to several locations.
What are the correct steps to stop the SQL Server merge replication.  
What are the correct steps to restart the SQL Server merge replication.

Some questions about SQL2008 replication I want to ask.
If I want to set up 2 SQL servers, 1 server in HK, 1 server in South China,
they will replicate data each other.
The SQL server in HK I want to use MSSQL2008 Enterprise Edition.