Creating a Text Configuration Object

Create a text configuration for use with a text index.

Prerequisites

Database Version	Text Configuration Object Privileges
SAP Sybase IQ 15.3 and 15.4	Text configuration object to be owned by self – you must have RESOURCE authority. Text configuration object to be owned by any user – you must have DBA authority.
SAP Sybase IQ 16.0	Text configuration object to be owned by self – you must have the CREATE TEXT CONFIGURATION system privilege. Text configuration object to be owned by any user – you must have one of: CREATE ANY TEXT CONFIGURATION system privilege CREATE ANY OBJECT system privilege You must also have one of: ALTER ANY TEXT CONFIGURATION system privilege ALTER ANY OBJECT system privilege

The SAP Sybase IQ resource is authenticated and running.

Task

For detailed information on stoplists, in the SAP Sybase IQ documentation, see IQ-product-name Unstructured Data Analytics > TEXT Indexes and Text Configuration Objects > Text Configuration Objects > Text Configuration Object Settings > Stoplist Setting (STOPLIST).

In the Perspective Resources view, select the resource, and select Resource > Administration Console.
In the left pane, expand IQ Servers > Schema Objects, and then select Text Configuration Objects.
Click the arrow next to Text Configuration Objects and select New.
The Create Text Configuration Wizard appears.

On the Text Configuration Name page, specify

Option	Description
Select a resource for which the text configuration will be created	From the list, select the resource for which the text configuration object will be created.
Which user do you want to own the text configuration object?	From the list, select the user to own the text configuration object.
What do you want to name the view?	Enter a unique name for the new text configuration object; maximum of 128 characters.
For which database collation will this text configuration object be used	Each database has a CHAR collation and an NCHAR collation, configured when the database is created. Valid choices are: ISO_BINENG – Binary ordering, English ISO/ASCII 7-bit letter case mappings UCA – Standard default Unicode Collation Algorithm collation Default value is ISO_BINENG.
(Optional) Comment	Specify an option comment for the text configuration object.

Click Next.

On the Choose the Term Breaker page, specify:

Option	Description
Which term breaker algorithm should be used?	Select Generic or N-gram.
What is the minimum term length?	For Generic - Valid range is 1-60. Default value is 1. For N-gram - Not available.
What is the maximum term length?	For Generic - Valid range is 1-60. Default value is 20. For N-gram - Valid range is 1-60. Default value is 4.
(For database collation ISO_BINENG and Generic term breaker algorithm) (Optional) Use an external term breaker?	Select to use an external library function to break the text into terms, using one of these formats: function-name@library-file-name Windows-function-name@library-file-name.dll UNIX:UNIX-function-name@library-file-name.so

Click Next.
(For ISO_BINENG database collation only) (Optional) On the Specify an Option Prefilter page, select Use an external prefilter and specify the external prefilter function and library. Click Next.
(Optional) On the Specify the Stoplist page, indicate the terms to be ignored when building a text index. Separate terms with spaces. Terms in the stoplist are also ignored in queries.

Note: Many non-alphanumeric characters are ignored in stoplists; others (including spaces, apostrophes, and dashes) are interpreted as term delimiters. Consequently, including contractions and hyphenated terms may lead to undesirable results, even when you enclose the terms in quotes. How the stoplist is parsed depends on the term breaker and term lengths you specified in step 6.
Click Finish.

Next

Create a text index that uses your new text configuration.