I'm going to upgrade a server from SQL Server 2000 to 2005. There are about
20 subscribers and I want to keep the replication settings.
What will happen to the server after in-place installation of SQL Server 2005?
Can I keep the settings?

I came accross a problem with tran. replication on db which was detached
from 2005 and attached to 2008.
Logreader was failing with:
The process could not execute 'sp_replcmds' on 'serv1\IN1'. (Source:

I have a queue reader that recently started failing with the following error
msg -
Executed as user: DMN\wssql. Replication-Replication Transaction Queue
Reader Subsystem: agent [SSD05].09 failed. Queue Reader aborting.  The step

Hi,
We are using .Net 2.0 and Sql Server 2005 and Sql Express (Merge replication).
And we have 4 subscribers, everything was working well until yesterday. There
was a database change (column datatype change), and suddenly only one

Good afternoon,
we are having difficulties when using transactional replication.
After the snapshot is done successfully, this error comes up at the publisher:
" The row was not found at the Subscriber when applying the replicated

I am using merge replication and i configured  snap shot to run manualy using
RMO
objects. But i did not run the snap shot sofar.
Last month  i have restored my publication db.

We have the need to add columns to our replicated tables with one caveat.
In 2005 normally all you have to do is write out the Alter TAble script and
away you go.  But, (and this is it)...we need to insert these columns prior
to the GUID column.  It cannot come after the GUID or ...

I had some serious troubles with our merge replication which worked fine for 1,5 years
I have manually added data to a new copy of the data
When I want to publish again
My snapshot generator reports :

Hi Hi,
I've a few SQL Server CE clients subscribers to my SQL Server 2005
publication. Everything works fine. However in my SQL Server
management Studio (in my SQL Server 2005), I would like to see how

Have the requirement to setup merge replication for a client/server.
Client:  windows XP, SQL Express  2005, NOT on domain, workgroup
"workgroup"
Server:  windows 2003, SQL 2005, on Domain.

We are in the process of migrating to a SQL 2008 server with a whole whack
of publications (upwards of 58 pubs).  We had about 7 publications left when
we noticed that the snapshot agents remained in a "starting" state.
Basically nothing was getting copied to the subscriber, and ...

Merge process was unable to access row metadata at the 'Subscriber'
SQL 2005 version 09.00.3294.  Publisher with 4 subscribers.  3 of the
subscriptions are working okay (one is showing some conflicts but I
have a good idea why).  The fourth subscriber generates the metadata

SQL 2005 SP2 on Windows 2003 SP2 hosting Evault messaging archiving
1. Invoking "msdb.dbo.log_shipping_monitor_error_detail" gave 2 rows with
details on AgentID, AgentType, SessionID and Message"There is a time and/or
date difference between the client and server"; however, ...

I setup a merge replication in SQL 2008.  It works as designed and all is
synchronizing fine.  I created this replication for a reporting system, there
is a timestamp column in all the tables being replicated.  The developers
that created the system, planned on using the ...

In the process of putting log shipping between 2 environments I am getting
the error...
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
on the secondary box when it tries to restore the transaction files.