"Kyle Jedrusiak" <kjedrusiak@princetoninformation.com> wrote in message
news:epPuhv3wFHA.3812@TK2MSFTNGP09.phx.gbl...
> We have two tables that have full text indexes, currently both are using
> the same catalog.
>
> One table is much larger and the column being indexed contains more data.
>
> Would there be any advantage of seperating the indexes into tow seperate
> catalogs?
>
> Kyle!
>

"Kyle Jedrusiak" <kjedrusiak@princetoninformation.com> wrote in message
news:%23VlkPPDxFHA.3124@TK2MSFTNGP12.phx.gbl...
> This is good stuff. The article was good as well.
>
> We can't seperate the catalog onto a different drive as we only have a
> RAID5 setup with 6 physical drives and one logical drive.
>
> One table has over 100K records, the other over 94K records. It's not
> millions of records, but we are trying to tweak search performace as much
> as we can. I don't forsee ever adding 252 more catalogs anywhere in the
> future. So seperating the FTI for each table into it's own catalog
> shouldn't be an issue.
>
> Thanks
>
> Kyle
>
> "John Kane" <jt-kane@comcast.net> wrote in message
> news:OVq6y79wFHA.1456@TK2MSFTNGP11.phx.gbl...
>> Kyle,
>> This is one of those questions, where the answer is that it depends...
>> First of all, see SQL Server 2000 BOL title "Full-Text Search
>> Recommendations" - "There are also full-text indexing and searching
>> considerations when determining whether to include multiple SQL tables in
>> one full-text catalog versus one SQL table per full-text catalog. There
>> is a trade-off between performance and maintenance when considering this
>> design question with large SQL tables and you may want to test both
>> options for your environment. If you choose to have multiple SQL tables
>> in one full-text catalog, you incur the overhead of longer-running
>> full-text search queries as well because incremental populations will
>> force the full-text indexing of all other SQL tables in that full-text
>> catalog. If you choose to have a single SQL table per full-text catalog
>> and have multiple SQL tables full-text indexed, you have the overhead of
>> maintaining separate full-text catalogs with a total limit of 256
>> full-text catalogs per server."
>>
>> Another consideration is whether or not you are using CONTAINSTABLE or
>> FREETEXTTABLE with RANK as having multiple tables in one FT Catalog can
>> affect the Ranking values...
>>
>> Hope that helps!
>> John
>> --
>> SQL Full Text Search Blog
>> http://spaces.msn.com/members/jtkane/
>>
>>
>> "Kyle Jedrusiak" <kjedrusiak@princetoninformation.com> wrote in message
>> news:epPuhv3wFHA.3812@TK2MSFTNGP09.phx.gbl...
>>> We have two tables that have full text indexes, currently both are using
>>> the same catalog.
>>>
>>> One table is much larger and the column being indexed contains more
>>> data.
>>>
>>> Would there be any advantage of seperating the indexes into tow seperate
>>> catalogs?
>>>
>>> Kyle!
>>>
>>
>>
>
>

"John Kane" <jt-kane@comcast.net> wrote in message
news:OVq6y79wFHA.1456@TK2MSFTNGP11.phx.gbl...
> Kyle,
> This is one of those questions, where the answer is that it depends...
> First of all, see SQL Server 2000 BOL title "Full-Text Search
> Recommendations" - "There are also full-text indexing and searching
> considerations when determining whether to include multiple SQL tables in
> one full-text catalog versus one SQL table per full-text catalog. There is
> a trade-off between performance and maintenance when considering this
> design question with large SQL tables and you may want to test both
> options for your environment. If you choose to have multiple SQL tables in
> one full-text catalog, you incur the overhead of longer-running full-text
> search queries as well because incremental populations will force the
> full-text indexing of all other SQL tables in that full-text catalog. If
> you choose to have a single SQL table per full-text catalog and have
> multiple SQL tables full-text indexed, you have the overhead of
> maintaining separate full-text catalogs with a total limit of 256
> full-text catalogs per server."
>
> Another consideration is whether or not you are using CONTAINSTABLE or
> FREETEXTTABLE with RANK as having multiple tables in one FT Catalog can
> affect the Ranking values...
>
> Hope that helps!
> John
> --
> SQL Full Text Search Blog
> http://spaces.msn.com/members/jtkane/
>
>
> "Kyle Jedrusiak" <kjedrusiak@princetoninformation.com> wrote in message
> news:epPuhv3wFHA.3812@TK2MSFTNGP09.phx.gbl...
>> We have two tables that have full text indexes, currently both are using
>> the same catalog.
>>
>> One table is much larger and the column being indexed contains more data.
>>
>> Would there be any advantage of seperating the indexes into tow seperate
>> catalogs?
>>
>> Kyle!
>>
>
>