SQL Server事务日志
[英]SQL Server Transaction Logs
问题描述
We are running an AlwaysOn SQL Server database with 2 servers. 
我们正在运行带有2个服务器的AlwaysOn SQL Server数据库。 All runs great but we do have massive data changes every day. 一切运行良好，但是我们每天确实有大量的数据更改。 Our DB is around 60GB but we update data very often and take trans log backups every day but still growth exceeds 100GB to 300GB on transaction logs. 我们的数据库约为60GB，但我们经常更新数据并每天进行跨日志备份，但事务日志的增长仍然超过100GB至300GB。
Is there any way to keep the transaction logs to 60GB (recommended size) and if it exceeds that, overwrite previous logs? 有什么方法可以将事务日志保持为60GB（建议大小），如果超过60GB，则覆盖以前的日志？
Any suggestions are appreciated. 任何建议表示赞赏。
Thank you. 谢谢。
1 个解决方案
解决方案1
1 已采纳 2018-09-17 05:40:10
If you don't need Transaction Log for DR purpose then just make it in SIMPLE recovery model and take a full backup once in a day. 如果不需要出于灾难恢复目的的事务日志，则只需使其成为SIMPLE恢复模型，然后每天进行一次完整备份。 and i don't understand why you are taking Transaction log once in a day. 而且我不明白为什么您每天要记录一次事务日志。
I think so it should be with in at least 15 mins interval. 我认为应该至少间隔15分钟。 Because you will loss of the data after last Transaction backup. 因为您将在上次事务备份之后丢失数据。 so as a process and good feature of MS SQL Server, make it with small interval and move it to another server for safe purpose as part of Log-Shipping. 因此，作为MS SQL Server的一个过程和良好功能，请使其间隔较小，并出于日志目的将其安全地移至另一台服务器。
声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.