Under what circumstances would it be advantageous to create more than one Full Text Catalog?

I need to assign a table/field to a Full Text Catalog to enable full text searching.  Should I create a new FTC or use the existing one (it only has one table/field assigned to it).  Is there an advantage to having multiple FTCs?  Don't be shy, school me :)
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

lcohanDatabase AnalystCommented:
I believe the following recommendations from SQL Recommendations from SQL Server 2008 Books Online listed below should give you a pretty good picture of when/how to group FT indexes per single/multiple Catalogs. The answer would also depend a lot of the size of the table(s)/index(es) to be FT indexed and the number of data changes that need to be propagated to the FT Catalog(s).

from SQL Server 2008 Books Online...
We recommend associating tables with the same update characteristics (such as small number of changes versus large number of changes, or tables that change frequently during a particular time of day) together under the same full-text catalog. By setting up full-text catalog population schedules, full-text indexes stay synchronous with the tables without adversely affecting the resource usage of the database server during periods of high database activity.
When you assign a table to a full-text catalog, consider the following guidelines:
1. Always select the smallest unique index available for your full-text unique key. (A 4-byte, integer-based index is optimal.) This reduces the resources required by Microsoft Search service in the file system significantly. If the primary key is large (over 100 bytes), consider choosing another unique index in the table (or creating another unique index) as the full-text unique key. Otherwise, if the full-text unique key size exceeds the maximum size allowed (900 bytes), full-text population will not be able to proceed.
2. If you are indexing a table that has millions of rows, assign the table to its own full-text catalog.
3. Consider the amount of changes occurring in the tables being full-text indexed, as well as the total number of rows. If the total number of rows being changed, together with the numbers of rows in the table present during the last full-text population, represents millions of rows, assign the table to its own full-text catalog.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
MariaHaltAuthor Commented:
Thank you!
lcohanDatabase AnalystCommented:
SQL FullText is a fairly large topic and as good as the feature may be it can cause (sever sometimes) performance issues if not properly configured  therefore depending  of the size of your tables/FT indexes please pay attention to factors that can impact performance as described under best practices:

MariaHaltAuthor Commented:
Thanks again!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.