Review the solution and discussion in the video The transaction log for database 'DB' is full due to 'REPLICATION'. 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.
Check out the highest-rated Automating ETL course on Udemy, if you're interested in data.
As a note for viewers of the YouTube channel: the Truth In Information series has been removed. Going forward, I will be teaching a private course on finding truth in information with applications in research. As of now, this course will not be offered through digital means but will require users to sign up and be present in person.
YouTube | Automating ETL | T-SQL In 2 Hours | Consumer Guide To Digital Security
