How to load licensed third-party broken characters

SQL Server 2008 R2 includes licensed third-party disconnections in the following languages:

• Danish

• Polish
• Turkish

These broken characters are available, but are not installed by default. You must manually register them and add them to the lcid list that supports full-text indexing and query.

Prerequisite Information

You need the following information to load the delimiter:

• The instance name of each SQL server instance on which the Delimiter is to be registered.

• The ftdata path of each instance.

  After obtaining the instance id, You must retrieve the ftdata
  The folder is specific to the corresponding path of the instance. This path is used when you add configuration values for dictionary and synonym library files in a specified language.

Obtain the Instance name of each SQL server instance

1. Click"Start"And then click"Run".

2. In"Run"In the dialog box"Open"Box, type regedit.
3. Click OK ". This will open the Registry Editor.
4. In the Registry Editor, it is the first SQL Server 2008 R2 instance (its instance id is
   Mssql10_50.mssqlserver) Select the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL10_50.MSSQLSERVER\SQL

   The right pane displays the Instance name and corresponding instance
   Id.

Important:
To obtain the name of another server instance, you must use its instance id in the Registry path instead of mssql10_50.mssqlserver.

Obtain the ftdata path for each instance

1. Click"Start"And then click"Run".

2. In"Run"In the dialog box"Open"Box, typeRegedit.
3. Click OK ".
4. In the Registry Editor
   Select the following registry for the instance:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\Instance_id\MSSQLServer, WhereInstance_id
   For the first SQL server instance
   Mssql10_50.mssqlserver. The registry key value will be:

   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft
SQL Server\MSSQL10_50.MSSQLSERVER\Setup

   Display in the right pane
   FulltextdefaultpathValue, which contains the ftdata folder path specific to the instance. For example, for the first SQL Server 2008 r2
   For instances, this may be the default path:

   C: \ Program Files \ Microsoft SQL
   Server \ mssql10_50.mssqlserver \ MSSQL \ ftdata

Register delimiter and related language components

The Installation Process of third-party broken characters licensed by Microsoft is divided into three phases. The following table summarizes these stages and their steps are described later in this section.

1. Add the broken characters and the com classid of the stem analyzer interface for the language to be registered, and add it as an entry to the Registry's
   <Instanceroot> \ MSSEARCH \ CLSID node.

2. Add the language items to the <instanceroot> \ MSSEARCH \ language node.
3. Add configuration values to specify the location of dictionary and synonym library files in the language.

Note:
This section uses the Danish delimiter as an example. The table following this topic provides the values required to install the delimiter for each language.

Phase 1: Add a break character and the com classid of the stem analyzer interface for the language to be registered

Note:
Incorrect registry editing can seriously damage your system. All important data on the computer should be backed up before the registry is changed.

Add the com class ID of these components for the Danish language:

1. Open the Registry Editor using the following methods:
   1. Click"Start"And then click"Run".

   2. In"Run"In the dialog box"Open"Box, typeRegedit.
2. In the Registry Editor
   Select the following registry for the instance:HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft SQL
   Server \ mssql10_50.mssqlserver \ MSSEARCH \ CLSID

3. On the menu bar, click"Edit", Click"New"And then click"Item".
4. Type{16bc5ce4-2c78-4cb9-80d5-440a68cc2b2d}.
5. Press enter.
6. In the right pane, right-click"Default Value"Registry value, and then click"Modify".
7. In"Edit string"In the dialog box"Value data"Box, type
   Danlr. dllAnd then click"OK".

8. Repeat steps 3 to 7 to replace the values in Step 4
   {83bc7ef7-d27b-4950-a743-0f8e5ca928f8}.

For a given language, perform the preceding steps and replace the values in steps 4 and 8 with the required language values. These values are listed below. In step 7
Replace the. dll name with danlr. dll.

Language	Item value in Step 4	The. dll name in Step 7	Item value in Step 8
Danish	{16bc5ce4-2c78-4cb9-80d5-440a68cc2b2d}	Danlr. dll	{83bc7ef7-d27b-4950-a743-0f8e5ca928f8}
Polish	{B8713269-2D9D-4BF5-BF40-2615D75723D8}	Lrpolish. dll	{CA665B09-4642-4C84-A9B7-9B8F3CD7C3F6}
Turkish	{23a9c1c3-3c7a-4d2c-b894-4f286459dad6}	Trklr. dll	{8df412d1-62c7-4667-bbec-38756576c21b}

Phase 2: add the corresponding language items
<Instanceroot> \ MSSEARCH \ language Node

Add the Danish item to this node:

1. Is the first SQL Server
   Select the following registry for the instance:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL10_50.MSSQLSERVER\MSSearch\Language

2. Repeat steps 3 to 5 in the previous process and useDanReplace the item name in step 4.

For a given language, perform the preceding steps and replace the name of the item in Step 4 with the values listed below for a specific language.

Language	Item Name in Step 4
Danish	Dan
Polish	PLK
Turkish	TRK

Phase 3: Add configuration values for the location of each language component for one language

Add configuration values for these components in Danish:

1. Select the registry entry entered in phase 2 above. For the first SQL Server
   Instance, which is:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL10_50.MSSQLSERVER\MSSearch\Language\dan

2. On the menu bar, click"Edit", Click"New"And then click"String value".
3. TypeTsaurusfile.
4. Press enter.
5. Right-click the added tsaurusfile registry value, and then click"Modify".
6. In"Edit string"Dialog Box"Value data"Box, typeTsdan. xml.
7. Click OK ".

Repeat steps 2 to 2 for other language components (Synonym library file, language (Region settings), break characters, and stem analyzer) in the corresponding language
7. The values required to register these components for Danish, Polish, or Turkish are as follows.

Danish Value

Repeat steps 2 to 7 to add each group of values listed below and replace each value with the language-specific value type (step 2), Value Name (Step 3 and step
5) and value data (Step 6 ).

Value Type in step 2	Value Name for Steps 3 and 5	Value Type in Step 6
String Value	Tsaurusfile	Tsdan. xml
DWORD Value	Region settings	00000406
String Value	Wbreakerclass	{16bc5ce4-2c78-4cb9-80d5-440a68cc2b2d}
String Value	Stemmerclass	{83bc7ef7-d27b-4950-a743-0f8e5ca928f8}

Polish Value

For polish, perform the preceding steps and use the values listed below in the steps. Select the registry entry for Polish in Stage 2 above. For the first SQL Server
Instance, which will be:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL10_50.MSSQLSERVER\MSSearch\Language\plk

Complete steps 2 to 7 to add the values listed below, replace the language-specific value types (step 2), value names (Steps 3 and 5) for each value) value Data (Steps
6 ).

Value Type in step 2	Value Name for Steps 3 and 5	Value Data in Step 6
String Value	Tsaurusfile	Tsplk. xml
DWORD Value	Region settings	00000415
String Value	Wbreakerclass	{CA665B09-4642-4C84-A9B7-9B8F3CD7C3F6}
String Value	Stemmerclass	{B8713269-2D9D-4BF5-BF40-2615D75723D8}

Turkish Value

For Turkish, perform the preceding steps and use the values listed below in the steps. Select the registry entry for Turkish in Stage 2 above. For the first SQL
Server instance, which will be:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL10_50.MSSQLSERVER\MSSearch\Language\trk

Complete steps 2 to 7 to add the values listed below, replace the language-specific value types (step 2), value names (Steps 3 and 5) for each value) value Data (Steps
6 ).

Value Type in step 2	Value Name for Steps 3 and 5	Value Data in Step 6
String Value	Tsaurusfile	Tstrk. xml
DWORD Value	Region settings	0000041f
String Value	Wbreakerclass	{8df412d1-62c7-4667-bbec-38756576c21b}
String Value	Stemmerclass	{23a9c1c3-3c7a-4d2c-b894-4f286459dad6}

Update the list of languages supported by full-text search

After a third-party Delimiter is loaded, you must refresh the full-text index and query the supported lcid list. To refresh this list, use Perform the following steps in the system stored procedure:

1. Load the new disconnected characters and filters in the server instance as follows:

   	Copy code
   EXEC sp_fulltext_service @action='load_os_resources', @value=1;

2. Update the language list as follows:

   	Copy code
   exec sp_fulltext_service 'update_languages';

The new language with broken characters is List in the directory view.