Quantcast
Channel: StackExchange Replication Questions
Viewing all articles
Browse latest Browse all 17268

Transactional Replication issue due to big Transaction Log in sql server 2008 r2

$
0
0

I want an answer of question and that would be highly appreciated

Scenario:

First of all i am an IT guy from Sports Field and using SQL Server 2008R2. I have 2 production servers server 1 and Server 2 both are using SQL Server Transactional Replication [whereas Server 1 is Processing Major Database Operations crawlers and xml parsers data translation and many more stored procedures. it’s a publisher] [Server 2 mostly contains Websites that are used to show sports data on website and it’s a subscriber]

  • Actual Data file size is around 3 GB on server 1
  • Actual Data file size is around 1 GB on Server 2

The problem is that Server 1’s Log file size is increasing with uncertainty let say it grows over the night and jumps to 14 – 15 GB normally if i do not shrink the size with simple recovery model. Usually i am using Full Recovery model because of Replication. I know that it’s pretty much load but that thing was not growing until i tried to make DB’s errors rectified.

Due to log size increase replication between both servers struck. some of my queries also contain nolock because previous problems until my joining was deadlocks in that DB. Now it’s around 85% less. :)

I already took and implement a Transaction log because someone posted that it might be helpful to take Log backup it helps to reuse the free space of log but there is no success indeed suppose a backup log which was using around 2 Gb log Once and had around 1600 MB free so the log backup which i initiated was around 400MB. but still the space 1600 MB was enaged to log.

please help / suggest a solution to automaticaly clear DB’s Transaction log. Summary.

  1. Irregular / uncertainty in growing of Transaction Log and not releasing space

  2. Transactional Replication between both servers stopped due to Transactional log (I think)

One more thing : i got an errors from log reader.

Error codes are (355, 298, 165, 382, 18456, 4060).

There are only 2 users sa, sqladmin


Viewing all articles
Browse latest Browse all 17268

Trending Articles