Wednesday, October 6, 2010

Unable To Shrink Replicated Transactional Log File In SQL Server

Clear the Replication Log from the database, after replicated the data sp_repldone is used to mark every transaction in the log to be marked as replicated to the distribution database.

Check if any open transactions are there in the database by running below query. 

USE AdventureWorks 
Go
DBCC OPENTRAN AdventureWorks 
Go 

To truncation of the transaction log when transactions pending replication are present. 

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

Caution:
This procedure can be used in emergency situations to allow truncation of the transaction log and when transactions pending replication are present.
The process could not execute sp_repldone/sp_replcounters. Using sp_repldone to SKIP a transaction. How long does it take for sp_repldone to execute. could not execute sp_repldone sp_replcounters. sp_repldone example. sp_repldone sql 2008. sp_repldone sql 2005. sp_repldone mark transactions distributed. sp_repldone.  sp_replcounters. Another log reader is replicating the database. Using sp_repldone to SKIP a transaction. Hot to shrink log file. unable to shrink log file. my log file is not shrinking. Log file does not shrink. Why is my LDF Log File so big. Help. My SQL Server Log File is too big. SHRINKFILE and TRUNCATE Log File in SQL Server 2008. SHRINKFILE and TRUNCATE Log File in SQL Server 2012. how to shrink log file in sql server 2012. Shrink database log file sql server 2005, Shrink database log file sql server 2008 R2, Shrink database log file sql server 2012,

0 comments:

Post a Comment