I've got a merge replication set up with the publisher running SQL Server
2005 Standard SP2 and the subscribers running SQL Server 2005 Express SP2.
Around 10 of the subscribers are working fine, but one is getting these
errors when running the synchronization (copied from the ...

I need to remove a linked server and I am getting an error code 20854
indicating the publisher cannot drop the server because it is used as a
subscriber.  Is there a reference document anyone knows of that can explain
the proper process for removing linked servers.  I have tried ...

Help please.
I have had replication in sql server 2000 running fine for several years
now. We are now evaluating SQL Server 2008. I Installed the Enterprise
edition of SQL Server 2008 on a Windows Std Server 2003. I created two

We intend to create in one SQL instance located at Failover Cluster
Datacenter, about 250 database, each one with transactional replication to
many other remote subscribers. Are there any garantee that 250 log reader can
work together at the same distributor ?

Deal all,
I server_live I have 4 databases: the live_db, test_db, training_db
and development_db.
Now I would like to move test_db, training_db, and development_db to

Pull Subscription, Remote Distributor (on the Subscriber), not Immidate
Updating, Tranascactioal Replication with both boxes SQL2K SP4.
I have no idea what to do here. I highlight Log Reader Agent and all of them
simply say "The step did not generate any output. The step failed". I ...

HELP!
I had setup transactional replication and it was working great, but I had to
remove it due to some issues with the application/schema.  Unfortunately, I
did not use the Wizard to remove the publisher/distributor and now when I try

SQL 2005 - SP1
We had a server reboot last night and now my replication-monitor with message
'The initial snapshot for publication '' is not yet available on
Distributor-Subscriber tab and is NOT replicating to subscriber.

I have setup merge replication with sql 2005. I am trying to a add a
new table with a primary key (with NOT FOR REPLICATION set ) to the
replicated environment.
When I include the new table in the articles to be published i accept

We are having a problem with merge replication via the web. We usually get
the following message:
The merge process could not replicate one or more INSERT statements to the
'Subscriber'. A stored procedure failed to execute. Troubleshoot by using SQL

Total published database size 500GIG
I have a row filter criteria on 1 table in the published database that
takes up about 80 GIG.
I am using this as my row filtering criteria for the publication for

I am setting "Delete data. If article has a row filter, delete only data
that matches the filter." value for "Action if name is in use " property for
my articles in publication which supports web merge synchronization.
At subscriber i am having blank database with required schema ...

I have written custom conflict resolver in C# for my merge pull subscription
which synchronizes using web synchronization.
Based on some business rule i am rejecting updates and insert from
subscriber. These changes are not making to server (publisher) so far so

We have had a problem for the past 2 years with replication agents failing
with the following error.
--------------------------------------------------------------------------------------------
OUR ERROR:

Replication Monitor.
I know that data for monitor is stored in MSreplication_monitordata table.
But I couldn't find any way to clear that data e.g for subscriptions that no
longer exist?