Transaction Logs on Andy M Mallon - AM²

Is it possible to do a partial transaction log backup with SQL Server 2017? I don't have enough disk space to do a full backup

Fri, 15 Oct 2021 18:12:37 -0400

Question

Inherited a database server to maintain and found that the transaction log is 92 GB. My plan is to do the backup of that and get it brought back down to a regular size, then fix it. The problem is I don't have enough disk space on the machine to do the backup locally, then offload. Is there a way I can run the backup for a specified size or time period so I can do it in stages?

Can I use both Log Shipping and Transaction Replication at the same time?

Fri, 15 Oct 2021 11:36:11 -0400

Question

Good Morning, I have a SQL Server 2016 that is doing Log Shipping to a DR Site. I currently want to also to Replicate (Transactional) specific Tables to another Server for Reporting Purposes.

Will there be any issues or snafu’s I should be aware of? Can I have Log Shipping and Transactional Replication configured on the same Publishing Database?

SQL log file 2TB is not enough, now what?

Fri, 18 Oct 2019 12:04:01 -0400

Question

This is a hypothetical question, that flows from the answer by sepupic where they explain that 2TB is the physical limit for SQL log file.

if you need it more than 2Tb you add the second log file.

I have long held the belief that multiple log files are bad as outlined in the post Multiple Transaction Log files and performance impact

Can SQL Server 2016 log files be applied on SQL Server 2012

Tue, 15 Aug 2017 03:53:35 -0400

Question

This is in relation to a rollback scenario from a 2012 -> 2016 upgrade.

The scenario is that the SQL Server 2012 database is restored onto 2016 and log files applied until it is up to date. Then production systems are cut over to 2016. Database is kept at compatibility level for 2012. Subsequently, incremental logs from the 2016 instance are kept until the need to roll back (let's say 8 hours worth).

Transaction log growth during BACKUP

Mon, 10 Apr 2017 08:06:37 -0400

Over on Stack Exchange, someone asked why their transaction log was growing very fast during a full backup. An interesting tidbit to this question is that the database is in SIMPLE recovery – so the log should stay tiny, right?

Wrong. While taking a full backup of the database, SQL Server is unable to reuse the transaction log for the duration of the backup, even if the database is in SIMPLE recovery. If your database is very busy, or backups take a long period of time, this can require a large transaction log, even if the database is in SIMPLE recovery.

Why do I have to backup a transaction log twice for it to shrink?

Fri, 07 Apr 2017 06:42:17 -0400

Question

This question was attempted twice on experts-exchange with no real answer.

I know that I should not shrink the log file - that is not the question.

If you feel like answering that one should not do it- that has been confirmed many times yes and it is not the goal of this question.

Transaction log is growing very fast

Wed, 05 Apr 2017 19:45:50 -0400

Question

One of our SQL Server 2014 database transaction logs is growing very fast and I cannot find the root cause for this.

Database in Simple recovery mode. During full backup the log file grows to its limits (800GB) and backup fails.

Podcast: Mirroring, Availability Groups, Replication, and Log shipping

Wed, 31 Aug 2016 09:29:03 -0400

Have you ever wondered what the best option is for making your data available in your environment? I was asked by Carlos L Chacon (blog|twitter) to be part of a panel on his podcast for an episode discussing some of the options–availability groups, mirroring, log shipping, and replication. We cover each topic in detail and explain the positives and negatives of each one.

Will Transaction Log backup to Nul break Always On Availability Group configuration?

Mon, 31 Aug 2015 23:08:35 -0400

Question

Imagine we have two nodes participating in SQL 2012 AO. This is a test instance. During one of the index rebuild operation the log was grown up really big (250 GB). We are unable to back it up due to space constraint. What if we backup the Tlog to Nul (just to shrink it down) – will that break Always On?