SQL Server Full-Text Search: Hung processes with MSSEARCH wait type

Posted by CheeseInPosition on Stack Overflow See other posts from Stack Overflow or by CheeseInPosition
Published on 2008-09-05T17:34:43Z Indexed on 2010/03/23 0:51 UTC
Read the original article Hit count: 627

We have a SQL Server 2005 SP2 machine running a large number of databases, all of which contain full-text catalogs. Whenever we try to drop one of these databases or rebuild a full-text index, the drop or rebuild process hangs indefinitely with a MSSEARCH wait type. The process can’t be killed, and a server reboot is required to get things running again. Based on a Microsoft forums post[1], it appears that the problem might be an improperly removed full-text catalog. Can anyone recommend a way to determine which catalog is causing the problem, without having to remove all of them?

[1] [http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2681739&SiteID=1] “Yes we did have full text catalogues in the database, but since I had disabled full text search for the database, and disabled msftesql, I didn't suspect them. I got however an article from Microsoft support, showing me how I could test for catalogues not properly removed. So I discovered that there still existed an old catalogue, which I ,after and only after re-enabling full text search, were able to delete, since then my backup has worked”

© Stack Overflow or respective owner

Related posts about sql-server

Related posts about full-text-search