Disclaimer: This article is a blogger original article, shall not be reproduced without the bloggers allowed. https://blog.csdn.net/zhengjuqiang/article/details/84953972
This is the wrong question, since that is the log log file growth is too long, the configuration log 10% growth from expansion 2014GMax, but if the log is too large 50G, 10% growth is 5G, so that the database assign long time, in this time period requested data, the data is non-responsive, i.e., timeout expires.
USE[master]
GO
ALTER DATABASE THTreasureDB SET RECOVERY SIMPLE WITH NO_WAIT
GO
ALTER DATABASE THTreasureDB SET RECOVERY SIMPLE
GO
USE THTreasureDB
GO
DBCC SHRINKFILE (N’THTreasureDB_log’ , 2, TRUNCATEONLY)
GO
USE[master]
GO
ALTER DATABASE THTreasureDB SET RECOVERY FULL WITH NO_WAIT
GO
ALTER DATABASE THTreasureDB SET RECOVERY FULL
GO