SQL日志缩小主要位置的高可用性 [英] SQL Log Shrinking on high availability on Primary location

问题描述

亲爱的所有人，

我们的SQL Server日志文件收缩存在问题。当我们尝试缩小日志时我们必须断开服务器与高可用性组的连接并再次加入。除非它不允许我们缩小日志。请分享您在这个
问题上的专业知识。

We have an issue with our SQL Server Log file shrinking. When we try to shrink out Logs We have to disconnect the servers from the high availability group and join again. Unless it will not allow us to shrink the logs. Please share your expertise on this issue.

谢谢！

推荐答案

您运行DBCC SHRINKFILE并且未清除日志文件？是同步还是异步？

You run DBCC SHRINKFILE and the the log file is not cleared? Is that sync or async?

如果你运行DBCC LOGINFO（dbid）那么 你看到 状态底部的值 列= 2？如果你这样做意味着SQL Server需要某种方式 交易并且必须承诺 

If you run DBCC LOGINFO (dbid) do  you see  the values at the bottom in the state  column =2? If you do that means SQL Server somehow needs  the transactions and must committed 

这篇关于SQL日志缩小主要位置的高可用性的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！