Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2001-11-02 : 09:00:14
|
| Rich writes "I am having some problems with my full text catalog. I have a table which contains about 200k rows. Originally i was going to do a full population each night, yet i now wish to update every hour and thus need an incremental population. I have added a timestamp field to the table and scheduled a job to do an incremental population every hour. Around 1500 records get updated each hour yet it not only does it take around 30- 45mins (a similar time to the full population) but it also completely maxes out the processors and causes many other operations to falter.Could it be that the timestamp field is not being taken into account and it is in fact doing a full population each time? If so, how can i ensure that it is only reindexing the changed records? I believe that the incremental population should take significantly less time to do than a full population and it is something that needs to occur in my database so that the data being searched on is as up to date as possible." |
|
|
|
|
|
Full Text Indexing Problems