Can't run sp_repldone/sp_replcounters
What's this mean & what can I do to resolve it?  I've deleted everything & set everything back up several times.....
Thanx!

I am getting this message & don't know what it means or what to do, new to Sql 2005 replication & getting ready to take my production 2000 server to 2005, but not until I can see this running replication successfully in test.
The log scan number (18875:16062:5) passed to log scan ...

Simple question, I hope, can we setup push snapshot and transactional
replication from SQL2K to SQL Express?
We have successfully set up SQL2K to SQL2005, but turns out the client
is wanting to use SQL Express instead, and we are struggling getting

When setting up replication, is the wizard supposed to automatically add the
IDENTITY_INSERT ON statement to the insert statement for tables with an
identity column?

I am using a merged publication. Right now this issue refers to a audit
table. The primary key to the audit table is right now ATID field. However I
did not realize that ATID field  wil have duplicate value if I am to capture
each of the field in the main table that is being ...

SQL Server 2000 SP4 Standard Edition
We would like to move our distributor database to another server. What is
the best way to do so?
I will appreciate your response.

We have two servers; one in US and one in Europe. They are SQL Server 2005
Ent.
Both have one databases. Both dbs have the same schema, but partially
different data.

I set up a new transactional push replication between two SQL Server
2000 SP4.
I did create the replicationprocs with SP_scriptpublicationcustomprocs
'...' and applied the result on the subscriber.

In sql server 2000, we used customized replication stored procedure instead
of using system stored procedures, include insert, update, and delete stored
procedures, to improve the replication performace. I don't know if it is
helpful in sql server 2005. Do I need to write those ...

I have the following two questions about merge replication in SQL
Server 2000:
If a conflict occurs when synchronizing subscriber with publisher I
can view conflict data in Conflict Viewer and resolve or remove it.

All--
I'm testing replication locally with copies of production servers.
For some reason metadata replication commands (e.g., exec
sp_helppullsubscription, exec sp_helpmergepullsubscription) are being

I am using SQL Server 2005 enterprise edition SP2. This is quite
disappointing me to when I am going to configure the publication I am getting
the following error
TITLE: New Publication Wizard

I have a replicated db running 2 years without problem. both are sqlserver
2000 sp4 patch 2171, one has a publication settings and uses another one as
remote distributor. both publisher db and distribution db are on full mode,
backup very 15 minutes with distribution db has ...

I have a SQL 200 Server at both ends and I have a transactional replication
that is pushing to a subscriber and it is scheduled to run at a certain time
so the snapshot runs at 22:00 and distribution at 22:40 and I am getting the
following error:

Right now, tied to a particular xact_seqno within msrepl_commands, we have
around a million + commands that consumes a lot of CPU resources when the
distribution agents are all contending to push the underlying commands out
to the subscribers.