• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 215
  • Last Modified:

full text index

First of all I would like to beg your perdon for my english.

My question is about full text index.

from the performance point of view, is it better one catalog per table or one catalog for all the tables?
what in your opinion should be the limits in terms of the number of fields per table than must be include in then index in order to keep the date base performance? (I have a table with 232 fields and around 72 varchar and text fields that can be included and I dont know if is a good idea to include all of them)
0
lespbaj
Asked:
lespbaj
1 Solution
 
Eugene ZCommented:
..it depends on your environment:
The sql server 2008 will store FTS catalogs in DB ndf files: so probably to keep  each FTS index in it's own ndf - is not so bad idea

read
Best Practices for Integrated Full Text Search (iFTS) in SQL 2008

http://blogs.msdn.com/b/sqlcat/archive/2008/11/06/best-practices-for-integrated-full-text-search-ifts-in-sql-2008.aspx
--

SQL Server 2008 Full-Text Search: Internals and Enhancements
http://msdn.microsoft.com/en-us/library/cc721269(v=sql.100).aspx
0
 
Alpesh PatelAssistant ConsultantCommented:
It based on your field access. The files which you use more ti get filter out data create index on that field.
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now