I have two SQL Server 2000 servers using Transactional Replication with Push
subscription. Once it was set up, the distribution agent kept displaying "the
process is running and is waiting for a response from one of backend
connections" while the subscriber's transaction log file ...

After some very helpful advice from this forum, I have set up Merge
replication on 2 SQL Server and 1 SQL Express machines. One of the SQL
Servers has been configured as the publisher and the other one and the SQL
Express as subscribers.

      I have a issue with merge replication. I have setup replication
between 2005 and 2000 SQL Server. But, i cannot initiate replication bcaz
"JOB HISTORY" says the following:
step ID           1

I have a SQL2005SP1 publushed database with 4 merge subscribers, everything
has been running just fine for month now.  Yesterday two of the subscribers
stopped merging.  This happened when I installed Reporting Services on the
publisher.

SQL 2000: I have a transactional replication with an updatable subscriber.
The update method at the subsrciber is set to "queued" (otherwise inserts on
the subscriber will fail in case the publisher is off). This has been working
fine until yesterday 14:19. Since then inserts on ...

i have SQL 2005 SP1 on two Windows 2003 R2 Enterprise Servers. One is the
main DB and the other is just being replicated to.
I would like to make some changes to existing tables as well as add some
tables to a database which has been published and subscribed to by the second

I have merge replication running with the following topology:
SQL2K5(PUB)------->SQL2K5(REPUB/SUB)------->SQLExpress2K5(SUB)
So, I have a publication which is pulled by two
republishers/subscribers.  My clients pull from one of the two

We have SQL 2000 servers connected by transactional replication. We are
using custom SPs to push data accross. Suddenly this morning, replication
started acting strange, to be more descriptive -
one of the articles has 8 columns and is defined to use MCALL type SP for

sp_publication_validation does not seem to show any errors/mismatches
after I delete a bunch of rows from a subscribed table. The ManStud GUI
validation function works fine and catches the mismatch in row counts.
use opeidev

I am trying to duplicate our production environment in QA.  It has a
number of fairly large published and subscribed databases on 3 different
servers.  I am planning to put all of them on one QA server.
Would like to be able to do this with nightly refresh of all data from

I've found that I'm doing this incorrectly and need some assistance.
What would be the proper way to adjust the length of a column's datatype
when I have transactional replication setup?
I've attempted to drop the column using sp_repldropcolumn and got the

My main question is whether the operation is atomic or not. For
snapshot replication in sql server, how does the subscription server
apply the table change - is it a drop/create, or a truncate/bcp? And is
it wrapped in a transaction.

Is there any licensing requirement for either push/pull merge replication
from SQL 2005 Standard Edition (Publisher) to SQL 2005 Express (Subscriber),
we have a per processor license.
Thanks in advance

Is there any way of preventing this stored procedure from truncating the
final scripts it produces (for sp_MSins_*, sp_MSUpd_* and sp_MSDel_*) if a
large number of columns are used in the replication model?
Thanks

I am trying to re-create a dynamic snapshot job we once had on our server
using the same name, however I am unable to do so.  The old dynamic snapshot
job has been dropped, but even after running the replication cleanup jobs, I
am unable to re-use the name.  Upon further ...