Transaction log grows out of space

AnneW 61 Reputation points

We recently have an issue after each month outage reboot MS orchestrator server, then the transaction logs start to grow crazily and fill sql log drive, and also backup drive. We had to add big amount of spaces on transaction log drive and backup drive.
We never had this issue before the upgrade.

Every time we do a reboot, it will increase the transaction log and eventually make the log drive full.

Any one experiences this?

we do have many jobs that setup as running state using monitor activity to trigger the job start time, even so we never have this problem before.

We are using full recovery mode, and do transaction log backup frequently.


System Center Orchestrator
System Center Orchestrator
A family of System Center products that provide an automation platform for orchestrating and integrating both Microsoft and non-Microsoft IT tools.
219 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. XinGuo-MSFT 15,941 Reputation points


    When the transaction log grows out of space, it is usually due to one of two reasons: either there is a long-running transaction, or the recovery model is not being used correctly.

    If the recovery model is set to full, then the transaction log will continue to grow until a log backup is taken. If you do not need point-in-time recovery, then you can switch to the simple recovery model to avoid this issue.

    If there is a long-running transaction, then you will need to identify and terminate it to free up space in the transaction log.

    You can use the DBCC OPENTRAN statement in SQL Server Management Studio to check for long-running transactions.

    I hope this helps!