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 |
|
maximus_vj
Yak Posting Veteran
88 Posts |
 Posted - 2006-04-04 : 18:23:15
|
| Hello,We are using Full Text Search in our application on a table. So whenever you do a search we are getting timeouts (SQL Query timeout) on some of the search queries. If there are multiple words in the search queries, then there are usually no timeouts. But if we try to search for “numbers” or “test” then the page sometimes will timeout. The reason for the page timing out is the query takes longer to run. So we increased the Command Timeout on the SQL Command as a temporary fix. Current Setup: We have a separate full-text catalog for this table. We are doing the Full-Text Catalogs on the 5 text fields in this table. No of Rows: 764405Full-Text Catalog Size: 431 MB, (Item Count: 764292, Unique Key Count: 1117094)Indexes on this table: Clustered Index on PKTest_ID, Non –clustered indexes on internal_Id Current Population Schedule:We do a Full Population once a WEEK on Sunday at 2 AM and we do incremental population every one hour.Time it takes to do an incremental population: 32 minsTime it takes to do a Full Population: Do not knowIs there a way to optimize this?I am thinking of doing change tracking instead of incremental population.Are there any other approaches I can try out?Can I have multiple catalogs for the same single table?Thanksmaximus |
|
|
|
|
|
Full Text Search Issues