In the video, The transaction log for database 'DB' is full due to 'REPLICATION', we look at this error and what it means along with some possible solutions (architecture dependent). We do not want to develop the habit of micro-managing transaction logs, so we should consider sizing before setting up any architecture such as replication, ETL solutions, etc. As a note that's not mentioned in the video: since transactional replication uses the log and involves full recovery, we cannot switch to simple recovery without first disabling replication. Thus, we must be in a situation where we can make log adjustments if we cannot disable replication.
Consider these in the context of the video:
- What is an activity that we should avoid with the log?
- Why is development around the log of a database so important?
- Considering that this is an error we may face at some point, what are some architecture considerations regarding the log when we're replicating data?
In general, everything in a database relies around the log. For this reason, we want to consider how we plan for log growth from when we first create our database. If we do not make these plans appropriate, we'll run into a myriad of problems involving the log. Our log growth will also dictate that type of transactions that we allow. For this reason (and others), I would heavily monitor log growth for any database server where replication or availability groups are setup at minimum. Monitoring log growth, if allowed (in some contexts), may be a requirement across the board, but it's especially true when we have availability groups and replication setup.
One regular point I like to remind my audience, especially as of recent: we can often solve the same problem with a variety of techniques. While we look at one or two ways to solve the problem, these aren't the only ways we can approach this problem. The most appropriate solution to a problem is one in which you can troubleshoot quickly in the future and one in which you understand. In this case, prevention is more powerful than solving a problem at the last minute: the last minute solution will come with more costs (inconvenience). Be careful about applying solutions that solve a problem, but introduce new problems in the future.