I am trying to create a large insertion of records into a table with full text indexing. I have installed change tracking on auto.
Entries are inserted from another table, usually in amounts of about 50,000 at a time. In SQL Server 2008, it takes approximately 5 seconds to complete. But working in our 2005 live environment, it takes 10 minutes.
Looking at execution plans, it seems like inserting full-text tracking tables into a clustered index, which is a problem. The primary key column is the uniqueidentifierone highlighted with newsequentialid(). But while in 2008 the 1 Clustered Merge merged on fulltext_index_docidstatus, 2005 makes the Clustered Index Insert 50,000 times on fulltext_index_map.
Unfortunately, updating the server is not an option now. Disabling change tracking fixes the problem, but I really do not want to do this, because managing the population itself will not be pleasant. As a rule, change tracking is the fastest way to get new entries in a full-text index and priority.
Is there any way around this while maintaining change tracking?
source
share