Backing up the transaction logs

Viewing 1 post (of 1 total)
  • Author

  • Philip

    I have a SQL Server Standard edition 2008 R2 db with an external application that backs up the db hourly to a SAN. Recently, the db logs and the transaction logs grew so big that the db shut down and would not accept any more read/writes to the server.

    The Server is set to full recovery model.

    I have offloaded some of the older db and trans logs to another file server and I want to set a maintenance plan to back up the transaction logs every 30 mins. This is supposed to truncate log sizes when this happens. Since, we have hourly backups is it worth doing this? Also, it is supposed to truncate the transaction logs when a log back up is set but when I looked at the log files they seem to be the same size.

    I have scoured google but can’t seem to get my head around it.



Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.

External Sharing and Guest User Access in Microsoft 365 and Teams

This eBook will dive into policy considerations you need to make when creating and managing guest user access to your Teams network, as well as the different layers of guest access and the common challenges that accompany a more complicated Microsoft 365 infrastructure.

You will learn:

  • Who should be allowed to be invited as a guest?
  • What type of guests should be able to access files in SharePoint and OneDrive?
  • How should guests be offboarded?
  • How should you determine who has access to sensitive information in your environment?

Sponsored by: