I tested the Maximum Retention period of the distributor DB but my test
failed and I would like to know why?
Here after the scenario that I performed:
I set up a transactional replication with a pull subscription.

Distribution database files were lost because of the disk failure.
We decided to remove completely replication from the server.
I used exec sp_dropdistributor, sp_dropdistributiondb, sp_removedbreplication
I also run delete msdb..msdistributiondbs

Some of the database updates on the Publisher are not being downloaded
to the Subscriber.  However, all the changes at the subscribers are
being uploaded successfully to the Publisher.  But, when I do a
complete download to a new local database I get all the data from the

I have a problem with replicatin schema changes via ALTER TRIGGER.
Wondering why they are transferred correctly, but not executed I found
the problem in the exists clause which preceeds the statement.
Here is the excerpt from the sysmergeschemachange of the subscriber:

i have transactional replication that is running fine, the problem came out
when we neededto move production server. as quick way to create scripts i
used generate script wizard. in most cases it worked fine, however for a
couple of tables that use procs instead of insert ...

I've got a database that _was_ replicated at one point. The replication has
been removed, and doesn't exist any more.
BUT - there appears to be some replication artefacts hanging around for 4
objects.

Can anyone confirm what happens when either of 2 SQL 2005 servers configured
for continous merge replication are rebooted?
Will the replication just pick up and carry on, or must it be manually
started again?

I have created a merge pull replication from SQL Server 2005 to Windows
clients running SQL Express 2005. The clients should be able to work offline
with the replicated database and synchronize when on-line. In Windows XP this
is no problem: the Synchronize tab in the Tools menu ...

I am not very experienced in Sqlserver2k administration.  I do mostly
scripting. I need to replicate/synchronize/update data between our company
server at our head office in Massachusetts running Sqlserver2K standard
edition with a desktop at our Manhattan sales office running ...

Hi we have a database at 32 gb which is involved in snapshot replication. On
checking log sizes using dbcc sqlperf the log file for this database is
50Gb and is 91% full.
I really need to get this database log file shrunk is there anything I

Hi to everyone.
I have 2 sql servers 2000 running merge replication. Sometimes the
publisher has an error saying that it cannot connect to the
subscriber, and there is a red "x" on the replication agent. What I do

Hi All,
Currently we are using SQL Server 2005 Enterprise Edition with (SP2). I set
up the auto email to show status of transactional replication that I execute
the following statements: exec distribution.dbo.sp_replmonitorhelppulocation

Using SQL 2005 SP2 on Windows 2003.  I've got a database set up with
transactional replication.  There's one text field that occasionally gets
updated with an UPDATETEXT statement.  When I check the subscriber, it is
not receiving these changes. The UPDATETEXT statement has the ...

I'm using transaciton immediate replication on SS 2000 SP4.  The problem is
that replication will sometimes have problems, i.e. I'll go into Ent Mgr and
see the publisher is red and needs to resync'd.  The standard alerts that it
is re-trying don't really work - I'd like to get ...

SERVER_A: Windows 2003 Server with SQL Server 2005 SP2. This is the
corporative server for all our data. About 30 tables divided in 4
publications. Each publication contains the tables belongs at the same
database. This is the suscriber of one publication I describe below.