sp_repldone

Last Post 16 Dec 2008 11:42 AM by Shafiq. 4 Replies.
AddThis - Bookmarking and Sharing Button
Author Messages
Shafiq
New Member
New Member

--
15 Dec 2008 05:01 AM
My replicated db transaction log has grown to 2.7 GB.
Is there an estimate how how much time sp_repldone stored proc is required to execute.
Is there any chance running this stored proc can create more transaction log

DBCC OPENTRAN gives following information

Transaction information for database 'DbName'
Replicated Transaction Information:
Oldest distributed LSN : (0:0:0)
Oldest non-distributed LSN : (7390:337:1)

Thanks
Shafiq
Shafiq
New Member
New Member

--
15 Dec 2008 08:42 AM
I have two publication for this database. Data file size is only 7 MB.

1. Merge Replication with SQL2K box
2. Snapshot Replication with SQL2K5 box

I check the replication monitor and I don't see any problem. Please Guide me how to check this.

Thanks
Shafiq
Shafiq
New Member
New Member

--
16 Dec 2008 06:42 AM
Recovery Model is Full, Transaction Log & Full Backup is done everyday.

If I breakup the replication, does uncomitted transactions problem will go away. This is small database and I can recreate the replication once the transaction log is truncated. Tran. Log file size is 3 GB as of today and it is increase 1/4 GB everyday.

Thanks
Shafiq
Shafiq
New Member
New Member

--
16 Dec 2008 11:42 AM
Publisher is on SQL Server 2000 SP3,

Back to my original question,

Is there an estimate how much sp_repldone proc will take to run on 3GB transaction log?
Will the transaction log grow more after running this stored proc?
Will running this proc will solve the log growing issue?

I have only 5 GB left on my Log Drive and just try to find an estimate before running this proc.

Thanks
Shafiq
Shafiq
New Member
New Member

--
17 Dec 2008 07:31 AM
I ran this stored proc and it was pretty quick. No new transaction log added. Backup the log/db and successfully truncated the log.

EXEC sp_repldone @xactid = NULL, @xact_segno = NULL,
@numtrans = 0, @time = 0, @reset = 1

I will monitor and see if there any new open transaction using dbcc opentran.

According to BOL,
This procedure can be used in emergency situations to allow truncation of the transaction log when transactions pending replication are present. Using this procedure prevents Microsoft SQL Server 2000 from replicating the database until the database is unpublished and republished.

Do I need to unpublish and republish?

Thanks
Shafiq


Acceptable Use Policy
---