Hi,
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!