Microsoft KB Archive/908441

= Licensed third-party word breakers are not installed by default in SQL Server 2005 Community Technology Preview September 2005 =

Article ID: 908441

Article Last Modified on 3/10/2006

-

APPLIES TO


 * Microsoft SQL Server 2005 Developer Edition Community Technology Preview
 * Microsoft SQL Server 2005 Developer Edition for Itanium-based Systems Community Technology Preview
 * Microsoft SQL Server 2005 Developer x64 Edition Community Technology Preview
 * Microsoft SQL Server 2005 Enterprise Edition Community Technology Preview
 * Microsoft SQL Server 2005 Express Edition Community Technology Preview
 * Microsoft SQL Server 2005 Standard Edition Community Technology Preview
 * Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems Community Technology Preview
 * Microsoft SQL Server 2005 Standard x64 Edition Community Technology Preview
 * Microsoft SQL Server 2005 Workgroup Edition Community Technology Preview

-







Beta Information
This article discusses a Beta release of a Microsoft product. The information in this article is provided as-is and is subject to change without notice.

No formal product support is available from Microsoft for this Beta product. For information about how to obtain support for a Beta release, see the documentation that is included with the Beta product files, or check the Web location where you downloaded the release.



SYMPTOMS
Microsoft SQL Server 2005 Community Technology Preview (CTP) September 2005 includes licensed third-party word breakers for the following languages:
 * Danish
 * Polish
 * Portuguese-Brazilian
 * Portuguese-Iberian
 * Russian
 * Turkish

These word breakers are available. However, they are not installed by default in SQL Server 2005 CTP September 2005. Therefore, you must manually register these word breakers.

Note We recommend that you set the Microsoft Full-Text Engine for SQL Server (MSFTESQL) service to run under a low-privileged account.



Register the word breakers
To register a word breaker, you must use the following method:  Add the following information to the  registry subkey:  The Microsoft Component Object Model (COM) Class ID or Class IDs for the word breaker The stemmer interfaces for the language that you are using

Note  represents the instance root. Add a subkey to the  registry subkey for the language. Add configuration values that specify the location of the lexicon, noise word, and thesaurus files for the language.</li></ul>

Obtain instance IDs for multiple instances of SQL Server
The registry paths that are listed in this article are for the first instance of SQL Server 2005. This instance has instance ID MSSQL.1. If multiple instances of SQL Server exist, you must modify the registry paths by substituting the instance ID for that instance instead of MSSQL.1. To obtain the instance ID for an instance, follow these steps: <ol> Click Start, click Run, type regedit, and then click OK.</li> In Registry Editor, locate the following registry key for the first instance of SQL Server:

</li> In the right pane, the instance names and the corresponding instance IDs appear.</li></ol>

Obtain the instance-specific FTData folder path
After you obtain the instance IDs, you must obtain the appropriate instance-specific path of the FTData folder. You will use this path when you add configuration values that specify the lexicon, noise word, and thesaurus files for a language. To obtain the instance-specific FTData folder path, follow these steps: <ol> Click Start, click Run, type regedit, and then click OK.</li> In Registry Editor, locate and then click the following registry key for an instance of SQL Server:

 

Note  is MSSQL.1 for the first instance of SQL Server. Therefore, the registry key will be the following:

</li> In the right pane, the FullTextDefaultPath registry value appears. This value contains the instance-specific path of the FTData folder. For example, the instance-specific path for the first instance may be C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\FTData.</li></ol>

Install the word breakers
The following section describes how to install the word breakers for the following languages:
 * Danish
 * Polish
 * Portuguese-Brazilian
 * Portuguese-Iberian
 * Russian
 * Turkish

Note The following steps use the Danish word breaker as an example. The values that you must use to install other language word breakers are listed after each step.

Add the COM Class ID or Class IDs for the word breaker, and add the stemmer interfaces for the language that you want to use
To add a COM Class ID or Class IDs for these components, follow these steps: <ol> Click Start, click Run, type regedit, and then click OK.</li> In Registry Editor, locate and then click the following registry key for the first instance of SQL Server:

 

</li> On the Edit menu, point to New, and then click Key.</li> Type {16BC5CE4-2C78-4CB9-80D5-386A68CC2B2D}, and then press ENTER.</li> In the right pane, right-click the Default registry value, and then click Modify.</li> In the Edit String dialog box, type danlr.dll in the Value data box, and then click OK.</li> On the Edit menu, point to New, and then click Key.</li> Type {83BC7EF7-D27B-4950-A743-0F8E5CA928F8}, and then press ENTER.</li> In the right pane, right-click the Default registry value, and then click Modify.</li> <li>In the Edit String dialog box, type danlr.dll in the Value data box, and then click OK.</li></ol>

For other languages, use the registry key values that are listed in the following table. In step 6 and in step 10, replace danlr.dll with the DLL for the language that you want.

Add a subkey to the <InstanceRoot>\MSSearch\Language registry subkey for the language
To add a subkey to this registry subkey, follow these steps: <ol> <li>Locate and then click the following registry key for the first instance of SQL Server:

 

</li> <li>Repeat steps 3 through 4 in the &quot;Add the COM Class ID or Class IDs for the word breaker, and add the stemmer interfaces for the language that you want to use&quot; section. Replace the key name in step 4 with dan.

For other languages, replace the key name in step 4 with the value that is listed in the following table. </li></ol>

Add configuration values that set the location of the lexicon, noise word, and thesaurus files for the language
To add configuration values for these components, follow these steps: <ol> <li>Locate and then click the registry key that you added in the &quot;Add a subkey to the <InstanceRoot>\MSSearch\Language registry subkey for the language&quot; section. For the first instance of SQL Server, this registry key would be the following:

 

</li> <li>On the Edit menu, point to New, and then click String Value.</li> <li>Type NoiseFile, and then press ENTER.</li> <li>Right-click the NoiseFile registry value, and then click Modify.</li> <li>In the Edit String dialog box, type \noisedan.txt in the Value data box.

Note  represents the path that you obtained by following the steps in the &quot;Obtain the instance-specific FTData folder path&quot; section.</li> <li>Click OK.</li> <li>Repeat steps 2 through 6 to add the values that are listed in the following table for the Danish language. </li></ol>

For languages that differ from Danish, use the following values.

Polish language values
Locate and then click the registry key that you added in the &quot;Add a subkey to the <InstanceRoot>\MSSearch\Language registry subkey for the language&quot; section. For the first instance of SQL Server, this registry key would be the following:

 

Follow the steps in the &quot;Add configuration values that set the location of the lexicon, noise word, and thesaurus files for the language&quot; section by using the values in the following table.

Portuguese-Brazilian language values
Locate and then click the registry key that you added in the &quot;Add a subkey to the <InstanceRoot>\MSSearch\Language registry subkey for the language&quot; section. For the first instance of SQL Server, this registry key would be the following:

 

Follow the steps in the &quot;Add configuration values that set the location of the lexicon, noise word, and thesaurus files for the language&quot; section by using the values in the following table.

Portuguese-Iberian language values
Locate and then click the registry key that you added in the &quot;Add a subkey to the <InstanceRoot>\MSSearch\Language registry subkey for the language&quot; section. For the first instance of SQL Server, this registry key would be the following:

 

Follow the steps in the &quot;Add configuration values that set the location of the lexicon, noise word, and thesaurus files for the language&quot; section by using the values in the following table.

Russian language values
Locate and then click the registry key that you added in the &quot;Add a subkey to the <InstanceRoot>\MSSearch\Language registry subkey for the language&quot; section. For the first instance of SQL Server, this registry key would be the following:

 

Follow the steps in the &quot;Add configuration values that set the location of the lexicon, noise word, and thesaurus files for the language&quot; section by using the values in the following table.

Turkish language values
Locate and then click the registry key that you added in the &quot;Add a subkey to the <InstanceRoot>\MSSearch\Language registry subkey for the language&quot; section. For the first instance of SQL Server, this registry key would be the following:

 

Follow the steps in the &quot;Add configuration values that set the location of the lexicon, noise word, and thesaurus files for the language&quot; section by using the values in the following table.

Keywords: kbtshoot kbprb kbsql2005fts KB908441

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.