January 20, 2005 at 7:59 am
Where does FULLTEXTCATALOGPROPERTY get its information from?
If you run this command
SELECT dateadd (ss,FULLTEXTCATALOGPROPERTY ('word_search', 'PopulateCompletionAge'), '1/1/1990')
I am getting different results on each node of my cluster (using legato). It displays the last date the full text catalog was populated on each node not the same date. This is the path of the catalog D:\MSSQL\FTDATA and this drive is mirrored.
Any idea why the population date is differnet on each node. Does full text catalog store something also on the C: drive.
So where does FULLTEXTCATALOGPROPERTY get its information from?
January 21, 2005 at 9:40 am
Good question...
I believe that FULLTEXTCATALOGPROPERTY gets its metadata of the FT Catalog from Registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search\1.0\. I'll post back exactly where, but it is registry driven.
You might also be seeing different results based upon when various FT Populations has actually been done on each of your nodes in your cluster depending upon when you last failed over to that node and then ran a Full Population on that node.
Regards,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
John T. Kane
January 24, 2005 at 3:27 am
Thanks for that. If you could confirm the exact registry key which stores the date for FULLTEXTCATALOGPROPERTY for the last population date that would be great.
I am surprised that this information is only held in the registry and not in a SQL Server table. This makes it difficult for clustering services. We use Legato for this particular site but I wonder if this would have the same issues in Microsoft Clustering Services.
I did do a test upload and rebuild for the catalog on 1 node and then failed over to the second node. Both nodes returned the new catalog item which I uploaded which is good so I presume that catalog data is carried across just not the date of last population.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply