Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Managing thousands of full text indexing logs

Posted on 2011-03-18
4
Medium Priority
?
254 Views
Last Modified: 2012-05-11
Howdy Experts!

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?!?

-Thorin
0
Comment
Question by:Thorin
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
4 Comments
 
LVL 2

Assisted Solution

by:Thorin
Thorin earned 0 total points
ID: 35166188
One clarification - we have determined the log files are created by SQL Server on restart - not our application's indexing request.
0
 
LVL 20

Expert Comment

by:Marten Rune
ID: 35170479
Open a ticket with CSS

http://support.microsoft.com/kb/295539

It's worth to create a ticket regarding this. I have seen something similar on a forum, and the answer there was to turn this to CSS.

Good luck, and please report back to this thread to assist others.

//Marten
0
 
LVL 2

Accepted Solution

by:
Thorin earned 0 total points
ID: 35434671
Howdy Experts!

I opened a ticket with MS on this and they did not have any particular solutions.  Essentially...this is working as designed.  There is no documentation available on managing these logs, and there is no maintenance plan for managing them.  

To alleviate the problem we have created a batch file to remove the older logs as they are generated.  This is a temporary solution until we can break the SQL Server into multiple instances and reduce number of dbs to ~ 100 per instance.  

-Thorin
0
 
LVL 2

Author Closing Comment

by:Thorin
ID: 35458510
See above
0

Featured Post

On Demand Webinar: Networking for the Cloud Era

Did you know SD-WANs can improve network connectivity? Check out this webinar to learn how an SD-WAN simplified, one-click tool can help you migrate and manage data in the cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Naughty Me. While I was changing the database name from DB1 to DB_PROD1 (yep it's not real database name ^v^), I changed the database name and notified my application fellows that I did it. They turn on the application, and everything is working. A …
If you have heard of RFC822 date formats, they can be quite a challenge in SQL Server. RFC822 is an Internet standard format for email message headers, including all dates within those headers. The RFC822 protocols are available in detail at:   ht…
In this video, Percona Solution Engineer Rick Golba discuss how (and why) you implement high availability in a database environment. To discuss how Percona Consulting can help with your design and architecture needs for your database and infrastr…
Want to learn how to record your desktop screen without having to use an outside camera. Click on this video and learn how to use the cool google extension called "Screencastify"! Step 1: Open a new google tab Step 2: Go to the left hand upper corn…

670 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question