Restore replicated database to another server

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: johnZ (johnZ_at_discussions.microsoft.com)
Date: 10/22/04


Date: Thu, 21 Oct 2004 20:57:02 -0700

Hi,

I restored a replicated database backup(sql 7) to another sql 2000 with
recovery mode 'full'.
The sql 2000 server dose not have any replication setup, but after the
restore, the database transaction can not be truncated any more and keep
growing.

**Ran dump tran 'dbname' with truncate_only, got message:
The log was not truncated because records at the beginning of the log are
pendin
g replication. Ensure the Log Reader Agent is running or use sp_repldone to
mark
 transactions as distributed.

**Ran sp_repldon, got message:
1> exec sp_repldone @xactid=NULL,@xact_segno=NULL,@numtrans=0,@time=0,@reset=1
2> go
Msg 18757, Level 16, State 1, Server STOR19P11001, Procedure sp_repldone,
Line 1

[Microsoft][ODBC SQL Server Driver][SQL Server]The database is not published.

**Also tried sp_removedbreplication, but did not help.

**Following is the output of dbcc opentran:
1> dbcc opentran
2> go
Transaction information for database 'tradesdb'.

Replicated Transaction Information:
        Oldest distributed LSN : (0:0:0)
        Oldest non-distributed LSN : (8701:66:2)

any suggestions how to clear the transaction log and 'turn off' the
replication?

thank
johnZ



Relevant Pages

  • Re: Cannot use a CONTAINS or FREETEXT predicate on table...
    ... command from the context of the database I wish to publish. ... This database is not enabled for publication. ... The replication agent has been successfully started. ... Source: Microsoft SQL Native Client ...
    (microsoft.public.sqlserver.replication)
  • Re: Cannot use a CONTAINS or FREETEXT predicate on table...
    ... This database is not enabled for publication. ... The replication agent has been successfully started. ... Source: Microsoft SQL Native Client ...
    (microsoft.public.sqlserver.replication)
  • Re: Subscriber Transaction Logs Too Large
    ... Its not so critical to shrink the db files or transaction logs in SQL 2005. ... Director of Text Mining and Database Strategy ... Looking for a SQL Server replication book? ...
    (microsoft.public.sqlserver.replication)
  • Re: Subscriber Transaction Logs Too Large
    ... mentioned not shrinking the file too much on SQL 2000. ... SQL 2005 (Server B). ... alter database databaseName ... Looking for a SQL Server replication book? ...
    (microsoft.public.sqlserver.replication)
  • Re: Subscriber Transaction Logs Too Large
    ... mentioned not shrinking the file too much on SQL 2000. ... SQL 2005 (Server B). ... alter database databaseName ... Looking for a SQL Server replication book? ...
    (microsoft.public.sqlserver.replication)