July 10, 2014 at 2:10 pm
Hi,
Since migrating from SQL 2005 to 2008 the transaction log has grown significantly as the FTC is stored within the database and its activity is logged by the DB engine.
We've put the fulltext index into "manual" tracking mode rather than "auto" which prevents the automatic and unpredictable master merges and scheduling regular update populations. However for a 280Gb FTC its is filling our 500Gb transaction log.
Trying to truncate the log isn't working indicating that the FTS is trying to comlpete a single large transaction.
Any ideas on how we could tackle this problem?
July 14, 2014 at 3:46 am
The first option is to try doing more frequent log backups. If this does not keep the log size under control then you have to accept that a larger log size is needed, and provide the necessary disk space.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply