KB889708

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Pineda - 20 Dec 2004 17:07 GMT

Does anyone know if this affects when the FTS os on the second node to
incremental population?

Thxs.

Reply to this Message

John Kane - 21 Dec 2004 02:58 GMT

Pineda,
Ok, I found the KB article that you're referring to - "The full-text search
results that are returned in a clustered SQL Server 2000 environment may be
different when the active node changes" at
http://support.microsoft.com/default.aspx?scid=kb;en-us;889708

As this is a new KB article, and I don't have clustered environment to test
this, but I doubt it as the CAUSE section states that "This problem occurs
when the noise word file location is not replicated between the nodes in the
cluster. When SQL Server 2000 is installed in a cluster". So, in affect the
different results are caused by the language-specific noise word file not
being installed on the 2nd node, thus causing different to results when
failover occurs and makes the 2nd node the active node. Note, this assumes
an Active/Passive environment and not an Active/Active (or Multi-instance
model).

What is your clustered environment - Active/Passive or Active/Active? Are
you seeing the symptoms of this KB article in your environment?

Thanks,
John

> Does anyone know if this affects when the FTS os on the second node to
> incremental population?
>
> Thxs.

Reply to this Message

Pineda - 21 Dec 2004 16:25 GMT

Jhon,

My environment is active/passive, but my question is not it. The KB says the
results are different because the noise word file is not replicate in the
passive node, but my question is if it also influence in the incremental
population, because the gatherer process uses the noise word file too. Then,
when the FTS and SQL are in the second node, the FTS could be indexed the
noise words too, because my noise word file is not replicate in this node.

> Pineda,
> Ok, I found the KB article that you're referring to - "The full-text search
[quoted text clipped - 22 lines]
> >
> > Thxs.

Reply to this Message

John Kane - 23 Dec 2004 01:41 GMT

Pineda,
Yes, that is correct. In fact, all FT Population methods - Full, Incremental
as well as "Change Tracking" with "Updated Index in Background" enabled
access and use the language-specific noise word files during the FT Indexing
(or gatherer) process.

Hope that helps!
John

Signature

SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/

> Jhon,
>
[quoted text clipped - 31 lines]
> > >
> > > Thxs.

Reply to this Message

Pineda - 23 Dec 2004 14:31 GMT

Jhon,

Then, Why Microsoft don´t say it in the KB. Now, I have one problem,
because I had the FTS runs on the second node several days.

> Pineda,
> Yes, that is correct. In fact, all FT Population methods - Full, Incremental
[quoted text clipped - 51 lines]
> > > >
> > > > Thxs.

Reply to this Message

John Kane - 23 Dec 2004 18:26 GMT

Hi Pineda,
I'm not sure... I added the following statement in the comments section at
the bottom of the KB article:

"This KB article needs to clarify and add some additional information.
Specifically, that all FT Population methods - Full, Incremental as well as
"Change Tracking" with "Updated Index in Background" enabled access and use
the language-specific noise word files during the FT Indexing (or gatherer)
process."

So, the problem you're having on your second node is different than what is
in the KB article. Correct? I seems that you're saying that the Incremental
(?) Population on your second node is taking several days to complete.
Correct? If so, what is the number of rows in your FT-enable table or
tables? The number of row is the primary factor in determining approx. how
long a Full or Incremental Population will take to complete.

Thanks,
John

Signature

SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/

> Jhon,
>
[quoted text clipped - 56 lines]
> > > > >
> > > > > Thxs.

Reply to this Message

Pineda - 24 Dec 2004 09:31 GMT

Jhon,
First, Happy Crhistmas.
I do not have problems with the FTS, but since I have read the KB I
am worried because during several days I had the FTS in the second node and
therefore was indexing noise words.

Thanks.

> Hi Pineda,
> I'm not sure... I added the following statement in the comments section at
[quoted text clipped - 90 lines]
> > > > > >
> > > > > > Thxs.

Reply to this Message

John Kane - 24 Dec 2004 10:46 GMT

Pineda,
Ok. Have you applied the Registry changes to your second node as described
in the WORKAROUND section? If not, I'd recommend this. If you're worried
about the different results, you can use the Registry change (export from
your 1st note, and import to your 2nd node) and then run a Full Population
on your 2nd node as this then will ensure that both nodes will return the
same results.

And you have a Happy & Safe Christmas too!
John

Signature

SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/

> Jhon,
> First, Happy Crhistmas.
[quoted text clipped - 26 lines]
> > >
> > > Then, Why Microsoft don?t say it in the KB. Now, I have one

problem,

> > > because I had the FTS runs on the second node several days.
> > >
[quoted text clipped - 68 lines]
> > > > > > >
> > > > > > > Thxs.

Reply to this Message

Pineda - 29 Dec 2004 17:35 GMT

Jhon,
Now, I see other registry key
""HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ContentIndexCommon\LanguageResources\default\language
neutral" which is on the two nodes of cluster. I use neutral word noise.
Then, It can to mean that I don´t have the problem.

Do you know the different between this registry key and
""HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ContentIndexCommon\LanguageResources\override"

> Pineda,
> Ok. Have you applied the Registry changes to your second node as described
[quoted text clipped - 130 lines]
> > > > > > > >
> > > > > > > > Thxs.

Reply to this Message

John Kane - 30 Dec 2004 03:40 GMT

Pineda,
I've re-read the KB article (889708) again, to be sure I had the right
registry key and on my non-clustered server and I see the following registry
key with the additional path of "SQLServer" (default installation) and
"Language Neutral" (for the Neutral wordbreaker) and then values Locale,
NoiseFile and TsaurusFile under "Language Neutral", as follows:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ContentIndexCommon\LanguageResources\O
verride
\SQLServer
\Language Neutral
Locale = 0
NoiseFile = <drive_letter:\path>\FTData\SQLServer\Config\noise.dat
TsaurusFile = <drive_letter:\path>\FTData\SQLServer\Config\tsNEU.xml

While you see the following registry key on your two nodes:
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ContentIndexCommon\LanguageResources\
default\language neutral"

and this is not the Registry key referenced in the KB article 889708. What
you should see is:
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ContentIndexCommon\LanguageResources\
override" with the additional parameters, ie. SQLServer and "Language
Neutral" as I've described above. The KB article is a bit un-clear in this
specific issue and could use some improvement, IMHO.

What I'd recommend is that you export the following registry key from a node
where this registry key exists:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ContentIndexCommon\LanguageResources\O
verride

then import it to the 2nd node in your clustered environment, and after
you've confirmed a successful import, run a Full Population and run a test
SQL FTS query on both nodes to confirm that you get the same results.

Hope that helps!
John

Signature

SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/

> Jhon,
> Now, I see other registry key

""HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ContentIndexCommon\LanguageResources
\default\language

> neutral" which is on the two nodes of cluster. I use neutral word noise.
> Then, It can to mean that I don?t have the problem.
>
> Do you know the different between this registry key and

""HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ContentIndexCommon\LanguageResources
\override"

> > Pineda,
> > Ok. Have you applied the Registry changes to your second node as described
[quoted text clipped - 89 lines]
> > > > > > be
> > > > > > > > different when the active node changes" at

http://support.microsoft.com/default.aspx?scid=kb;en-us;889708

> > > > > > > > As this is a new KB article, and I don't have clustered
> > environment
[quoted text clipped - 35 lines]
> > > > > > > > >
> > > > > > > > > Thxs.

Reply to this Message

Pineda - 30 Dec 2004 10:35 GMT

Jhon,
I have explained myself very badly. I would like to say I have two
registry keys on one node:
""HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ContentIndexCommon\LanguageResources
\override" and
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ContentIndexCommon\LanguageResources
\default\language neutral"

and in the second node only have this registry key:
""HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ContentIndexCommon\LanguageResources
\default\language neutral"

The KB article only references the registry key :
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ContentIndexCommon\LanguageResources
\override"

The servers are Windows 2000 with SP4 and SQL 2000 SP3a, it was one
installation clear it was not an upgrade from SQL 7.0. My question is : So
that key serves each registry?

Jose Antonio Pineda.

> Pineda,
> I've re-read the KB article (889708) again, to be sure I had the right
[quoted text clipped - 207 lines]
> > > > > > > > > >
> > > > > > > > > > Thxs.

Reply to this Message