Tips for Setting Up Catalogs
Several issues should be considered when setting up full-text catalogs (note that your server hardware may limit your options):
Any table that has millions of rows or is at least a gigabyte in size should have its own catalog.
For very large catalogs, store the catalog files on separate drives.
If different tables are being used for different queries, build separate catalogs on separate drives to reduce disk contention.
If different tables have different update patterns, such as one being transactional and the other bulk-loaded periodically, place them in separate catalogs so that incremental population of one table won't affect the change-tracking population of another table. Population of catalogs is very resource-intensive and can slow queries severely.