I expect that since the catalog used to populate, but will no longer populate, this must have something to do with the data added to the table recently.
Do these symptoms match any known issues? What should I do to debug this issue? I'm stuck.
Please help. Thank you.
Dave McCall? Do the gatherer logs reveal anything? -- Hilary CotterDirector of Text Mining and Database StrategyRelevantNOISE.Com - Dedicated to mining blogs for business intelligence. This posting is my own and doesn't necessarily represent RelevantNoise's positions, strategies or opinions. Looking for a SQL Server replication book?http://www.nwsu.com/0974973602.html Looking for a FAQ on Indexing Services/SQL FTShttp://www.indexserverfaq.com <Dave McCall@.discussions.microsoft.com> wrote in message news:b6cf47d2-6c0a-4c82-a9f9-42f1d2b71454@.discussions.microsoft.com...I have a SQL Server 2000 database with the latest service pack (3?). For some time, I've had full-text indexing working. Eventually, one of my full-text catalogs failed to populate. After a rebuild, I still couldn't populate it. I dropped it and recreated several catalogs. Eventually, I was able to get all of the original tables into a full-text catalog that populates except one. The offending table has less than 4000 rows in it. It is now in its own catalog which refuses to populate. I can't find any errors in the Application Log that correspond to this catalog population failing.I expect that since the catalog used to populate, but will no longer populate, this must have something to do with the data added to the table recently.Do these symptoms match any known issues? What should I do to debug this issue? I'm stuck.Please help. Thank you.Dave McCall
No comments:
Post a Comment