I'd like to create a fulltext index on a larger table (close to 4 million records). However, this does not work when the index also contains statistical semantics.
Statistical semantics is set up on the server, and it works with smaller tables.
So what happens when I try to create the fulltext index with statistical semantics on?
- The server is quite busy, which is understandable. The database log expands quite a bit during index creation (by about 50 Gig). To me that seems a lot, but ok.
- Watching the status of the catlog you can see that it gets populated. Nice.
- But unfortunately it never finishes. The 'item count' and 'unique key count' properties of the catalog suggest that all records have been indexed, but population never finishes.
- What is worse, the server pretty much freaks out. That is, it runs at full CPU and memory usage on forever (I gave it half a day until I restarted)
What I found in the logs are messages like these:
Transaction (Process ID 45) was deadlocked on lock resources with another process and has been chosen as the deadlock victim.Rerun the transaction.
After restarting the SQL-Server the log gets filled with a lot of these:
spid16s Informational: Resuming full-text population for table or indexed view '[table name]' in database 'db-name' (table or indexed view ID '1705109165', database ID '6').Prior number of documents processed: 3328000, error encountered: 0.
The SQL-Server 2012 is a fresh install on a Windows Server 2012 with 32Gig of RAM. I encountered the same problem on my development machine, which is a Windows7 64 bit machine.
The only thing I found that resembles the problem described is the following
http://support.microsoft.com/kb/963659/en-us
However, we are dealing with a fresh SQL-Server 2012 install, and as I said the problem only occures if statistical semantics for the index is on.
Best regards,
Johannes