Managing thousands of full text indexing logs
Posted on 2011-03-18
I have a SQL Server 2008 R2 running on top of Windows Server 2008 R2 - 64 bit. The server hosts 345 unique databases for one application (multi-tenant). Performance is generally fine, but every week or so the server abends because it has created thousands and thousands of blank full text indexing logs. These log files are created only on restarting the SQL Server.
When the server restarts it creates the file with the name SQLFTxxxx.log.1.
The second time when restarted it will have the name SQLFTxxxx.log.2.
and so on..
We have created a batch file to remove older logs, but even one restart creates over 70,000 log files. And they are all blank!
Full text indexing is required for a search feature in the application....how can we better manage these logs?!?