Hi,
We had purged a lot of unwanted data from one of our replicated databases ,the data was purged from the non replicated articles
Planned to shrink the data file using (DBCC shrinkfile) to claim the space back .The dbcc was running more than 20 hrs .
we saw this morning that replication was lagging .
On looking at the replication monitor (Publisher To Distributor History ) says that (the Log reader Agent is scanning the transaction log for commands to be replicated .Apx 339000000 log records have been scanned ).
Checked the log file size of the DB its about 400GB .
Suspected that the log growth might be because of dbcc command and killed the dbcc and tried to shrink the log file which came to 200 gb ,but still the replication is not back to speed .
Can someone please explain the background process that happened in the above process which caused the above affect and any ideas on how to get the replication back to normal.
Thanks,
Jack