The author needs to get his facts straight and know the different capabilities of SQL Server 2000 and 2005. It sounds like the author has no experience of SQL Server 2005.
The full-text catalogs and indexes are not stored in a SQL server databases,
which means if you restore the database on another server you have to do a lot of effort to build that index again.
SQL Server 2000 and 2005 differ here. I believe 2005 backups the FTS data. It is very easy to rebuild a full-text index in either version!
Also you have to set up a job to maintain the changes to full-text index that means your index is not up to date
You don't have to have a job. You can do it manually, scheduled or automatically. I use the automatic method on a very large database without issue whatsoever. It is very quick to update the index often in milliseconds.
more over you have to start a service called Microsoft Full-Text Engine (MSFTE SQL).
And the problem with this is? That's right there is no problem!