Use the SybaseIQ Table Index Editor to specify properties for a table index in a physical model.
To define Sybase IQ table index properties
The SybaseIQ Table Index Editor opens.
Note: Click New on the toolbar to create a new index. Use the Enter filter text box to filter a very large list of indexes to quickly locate the one that you want to define.
Displays the table to which the selected table index belongs.
Positions the editor on the previous table index in the Navigation Grid.
Positions the editor on the next table index in the Navigation Grid.
Sorts the table indexes by alphabetic, reverse alphabetic, or index order. You select the method you want using the drop-down menu that opens after you click the Sort button.
Creates a new table index that becomes the current object in the editor.
Deletes the selected table index.
Accesses online help for the editor.
Lets you enter text to filter a large list of table index objects so you can quickly locate the one that you want.
Specifies to display FK (foreign key) indexes in the Navigation Grid.
Displays the physical name of the table index.
Displays the table index type.
Specifies to allow only unique values in the table index. Clear this check box to allow non-unique values.
Note: This option is unavailable when a primary or foreign key index is selected.
Specifies whether to have the index appear in the physical model only. If you want the index to appear in the logical model as a key group, clear the check box.
Note: This option is unavailable when a primary or foreign key index is selected.
Generates SQL during forward engineering. Clear the check box if you do not want to generate SQL.
Lets you specify an index type. Use the drop-down list to make a selection.
Lets you enter the delimiter to use when a column string is parsed into the words to store in that column's Word index.
Lets you specify the maximum word length limit allowed in a Word index.
The table index is defined and the SybaseIQ Table Index Editor closes.
Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |