SELECT fulltextserviceproperty('IsFulltextInstalled');

EXEC sp_configure 'show advanced option', '1';
GO
RECONFIGURE;
GO
EXEC sp_configure 'default full-text language';
GO

• If the language of the text in your XML documents matches the database server's default full-text language setting, continue preparing the database to store ArcSDE XML data. No changes will have to be made to the DBTUNE full-text language parameter.
• If the database server's default full-text language setting is neutral, the language of the server did not match one of the languages supported for linguistic analysis. If the language of the text in your XML documents is not one of the languages listed in the default full-text language option topic, you may be able to index and search your documents with some degree of success using the neutral setting if all words in your language are separated by whitespace and punctuation. If the neutral setting will not work for your language, third-party full-text indexing solutions may be available; after installing and configuring them correctly, you must set the XML_IDX_FULLTEXT_LANGUAGE DBTUNE parameter correctly to index and search your XML documents.
• If the language of the text in your XML documents does not match the database server's default full-text language setting and the language of your documents is supported for linguistic analysis, you must modify the value of the XML_IDX_FULLTEXT_LANGUAGE DBTUNE parameter to index the text in your XML documents using the appropriate language.
• If the XML column will contain XML documents written in more than one language, you must use the neutral setting. Stemming will not be performed when indexing the text when the neutral setting is used.

1. In SQL Server Enterprise Manager, click the plus sign (+) next to Microsoft SQL Servers, click SQL Server Groups, click the appropriate SQL Server, then click the plus sign next to Databases.
2. Right-click the database in which the XML column will be created.
3. Point to New and click New Full-Text Catalog.
4. Type a name for the full-text catalog in the Name text box. If you provide a name other than SDE_DEFAULT_CAT, you must modify the value of the XML_IDX_FULLTEXT_CAT parameter for the DEFAULTS keyword in the SDE_dbtune table. Click the browse button, navigate to the location where you want the full-text catalog to be stored, and click OK.
5. Click OK in the New Full-Text Catalog Properties dialog box.

1. In SQL Query Analyzer, select the database in which the XML column will be created using the drop-down list on the toolbar or by executing the USE command. For example:

USE spatial;



2. Check if the database has been enabled for full-text searching. For example, if the database is named spatial:

SELECT DATABASEPROPERTY('spatial', 'IsFulltextEnabled');



If the value 1 is returned, the database is already full-text enabled—skip to step 4.
3. Enable full-text searching in the database using the sp_fulltext_database procedure. The value of the action parameter must be enable. For example:

EXEC sp_fulltext_database 'enable';



Use this command carefully. A database only needs to be enabled once before the first full-text catalog is created. If the database is already full-text enabled and this command is run again, any existing full-text catalogs will be dropped and re-created. Subsequently, any searches performed on the existing full-text catalogs won't work until they have been repopulated.
4. Create a full-text catalog in the database using the sp_fulltext_catalog procedure. The value of the ftcat parameter defines the catalog's name. If you provide a name other than SDE_DEFAULT_CAT, you must modify the value of the XML_IDX_FULLTEXT_CAT parameter for the DEFAULTS keyword in the SDE_dbtune table. The value of the action parameter must be create. Optionally, the path parameter can be used to set the location on disk where the full-text catalog files will be stored. For example:

EXEC sp_fulltext_catalog 'SDE_DEFAULT_CAT', 'create', 'C:\Data\Fulltext'; 

1. In SQL Server Management Studio's Object Explorer, right-click the database server and click New Query. A new SQL Query Editor window appears in Management Studio.
2. In the SQL Query Editor window, type and then execute the following query to verify the full-text search engine properly installed.

SELECT fulltextserviceproperty('IsFulltextInstalled');

1. In SQL Server Management Studio's Object Explorer, right-click the appropriate SQL Server and click Properties.
2. Click Advanced under Select a Page on the left in the Server Properties dialog box.
3. The Default Full-Text Language value is shown in the page on the right under Miscellaneous. Leave this dialog box open.
4. In the SQL Query Editor window, type and then execute the following query to list all of the full-text languages supported by your version of SQL Server:

SELECT * FROM sys.fulltext_languages;



5. Compare the Default Full-Text Language value in the Server Properties dialog box to the list of languages and their values in the query window. The default full-text language should be set to match the language of the database server when SQL Server is installed if that language is supported for linguistic analysis.

• If the language of the text in your XML documents matches the database server's default full-text language setting, continue preparing the database to store ArcSDE XML data. No changes will have to be made to the DBTUNE full-text language parameter.
• If the database server's default full-text language setting is neutral, the language of the server did not match one of the languages supported for linguistic analysis. If the language of the text in your XML documents is not one of the languages listed in the default full-text language option topic, you may be able to index and search your documents with some degree of success using the neutral setting if all words in your language are separated by whitespace and punctuation. If the neutral setting will not work for your language, third-party full-text indexing solutions may be available; after installing and configuring them correctly, you must set the XML_IDX_FULLTEXT_LANGUAGE DBTUNE parameter correctly to index and search your XML documents.
• If the language of the text in your XML documents does not match the database server's default full-text language setting and the language of your documents is supported for linguistic analysis, you must modify the value of the XML_IDX_FULLTEXT_LANGUAGE DBTUNE parameter to index the text in your XML documents using the appropriate language.
• If the XML column will contain XML documents written in more than one language, you must use the neutral setting. Stemming will not be performed when indexing the text when the neutral setting is used.

For more information see the appropriate topics in SQL Server Books Online.
6. Close the Server Properties dialog box.

1. In SQL Server Management Studio's Object Explorer, click the plus sign (+) next to the appropriate SQL Server, then click the plus sign next to Databases.
2. Right-click the database in which the XML column will be created and click Properties.
3. Click Files under Select a Page on the left in the Database Properties dialog box.
4. Check Use full-text indexing in the page on the right if it is not already checked.
5. Click Permissions under Select a Page on the left.
6. Click the user who will own the XML column or the role to which they belong in the Users or roles list in the page on the right.
7. In the Explicit permissions for <user or role> list at the bottom of the page, scroll down until you see the References permission.
8. In the row for the References permission, check the box in the Grant column.
9. Click OK in the Database Properties dialog box.
10. Click the plus sign next to the database, then click the plus sign next to Storage.
11. Right-click Full Text Catalogs, then click New Full-Text Catalog.
12. Type a name for the full-text catalog in the Full-text catalog name text box. If you provide a name other than SDE_DEFAULT_CAT, you must modify the value of the XML_IDX_FULLTEXT_CAT parameter for the DEFAULTS keyword in the SDE_dbtune table.
13. Set other properties for the full-text catalog as appropriate; for example, defining the location on the file system where the full-text index files will be stored or making the catalog the default full-text catalog for the database.
14. Click OK in the New Full-Text Catalog dialog box.

1. In the SQL Query Editor window, type and then execute the following query to check if the database has been enabled for full-text searching. For example, if the database is named sde:

SELECT DATABASEPROPERTY('sde', 'IsFulltextEnabled');



If the value 1 is returned, the database is already full-text enabled—skip to step 7. If another value is returned, the database must be enabled for full-text searching using Management Studio before you can continue.
2. In SQL Server Management Studio's Object Explorer, click the plus sign (+) next to the appropriate SQL Server, then click the plus sign next to Databases.
3. Right-click the database in which the XML column will be created and click Properties.
4. Click Files under Select a Page on the left in the Database Properties dialog box.
5. Check Use full-text indexing in the page on the right.
6. Click OK in the Database Properties dialog box.
7. In the SQL Query Editor window, select the database in which the XML column will be created using the drop-down list on the SQL Editor toolbar or by executing the USE command. For example:

USE sde;



8. Create a full-text catalog in the database using the CREATE FULLTEXT CATALOG statement. If you provide a name other than SDE_DEFAULT_CAT, you must modify the value of the XML_IDX_FULLTEXT_CAT parameter for the DEFAULTS keyword in the SDE_dbtune table. You can optionally set other properties of the full-text catalog such as providing a location on disk where the files will be stored and setting the catalog as the default full-text catalog for the database. For example:

CREATE FULLTEXT CATALOG SDE_DEFAULT_CAT IN PATH 'C:\Data\Fulltext' AS DEFAULT; 



9. Grant REFERENCES permission on this full-text catalog to the user who will own the XML column, or grant this permission to the role to which the user belongs. For example:

GRANT REFERENCES ON FULLTEXT CATALOG :: SDE_DEFAULT_CAT TO dataOwners;

1. In SQL Server Management Studio's Object Explorer, right-click the database server and click New Query. A new SQL Query Editor window appears in Management Studio.
2. In the SQL Query Editor window, type and then execute the following query to verify the full-text search engine properly installed.

SELECT fulltextserviceproperty('IsFulltextInstalled');

1. In SQL Server Management Studio's Object Explorer, right-click the appropriate SQL Server and click Properties.
2. Click Advanced under Select a Page on the left in the Server Properties dialog box.
3. The Default Full-Text Language value is shown in the page on the right under Miscellaneous. Leave this dialog box open.
4. In the SQL Query Editor window, type and then execute the following query to list all of the full-text languages supported by your version of SQL Server:

SELECT * FROM sys.fulltext_languages;



5. Compare the Default Full-Text Language value in the Server Properties dialog box to the list of languages and their values in the query window.The default full-text language should be set to match the language of the database server when SQL Server is installed if that language is supported for linguistic analysis.

• If the language of the text in your XML documents matches the database server's default full-text language setting, continue preparing the database to store ArcSDE XML data. No changes will have to be made to the DBTUNE full-text language parameter.
• If the database server's default full-text language setting is neutral, the language of the server did not match one of the languages supported for linguistic analysis. If the language of the text in your XML documents is not one of the languages listed in the default full-text language option topic, you may be able to index and search your documents with some degree of success using the neutral setting if all words in your language are separated by whitespace and punctuation. If the neutral setting will not work for your language, third-party full-text indexing solutions may be available; after installing and configuring them correctly, you must set the XML_IDX_FULLTEXT_LANGUAGE DBTUNE parameter correctly to index and search your XML documents.
• If the language of the text in your XML documents does not match the database server's default full-text language setting and the language of your documents is supported for linguistic analysis, you must modify the value of the XML_IDX_FULLTEXT_LANGUAGE DBTUNE parameter to index the text in your XML documents using the appropriate language.
• If the XML column will contain XML documents written in more than one language, you must use the neutral setting. Stemming will not be performed when indexing the text when the neutral setting is used.

For more information see the appropriate topics in SQL Server Books Online.
6. Close the Server Properties dialog box when you are finished.

1. In SQL Server Management Studio Express, click the plus sign (+) next to the appropriate SQL Server instance, then click the plus sign next to Databases.
2. Right-click the database in which the XML column will be created and click Properties.
3. Click Files under Select a Page on the left in the Database Properties dialog box.
4. Check Use full-text indexing in the page on the right if it is not already checked.
5. Click Permissions under Select a Page on the left.
6. Click the user who will own the XML column in the Users or roles list in the page on the right.
7. In the Explicit permissions for <user or role> list at the bottom of the page, scroll down until you see the References permission.
8. In the row for the References permission, check the box in the Grant column.
9. Click OK in the Database Properties dialog box.
10. In the SQL Query Editor window, select the database in which the XML column will be created using the drop-down list on the SQL Editor toolbar or by executing the USE command. For example, if the database is named spatial:

USE spatial;



11. Create a full-text catalog in the database using the CREATE FULLTEXT CATALOG statement. If you provide a name other than SDE_DEFAULT_CAT, you must modify the value of the XML_IDX_FULLTEXT_CAT parameter for the DEFAULTS keyword in the SDE_dbtune table. For example:

CREATE FULLTEXT CATALOG SDE_DEFAULT_CAT;



You can optionally set other properties of the full-text catalog such as providing a location on disk where the full-text catalog will be stored and setting the catalog as the default full-text catalog for the database.