Custom Index


Based on their analysis, database administrators may identify and implement custom indexes (in addition to those maintained by SAM Pro) which enhance a particular system’s performance. Until this release, these custom indexes had to be re-implemented after each database conversion. This enhancement enables the DBAs or system administrators to store custom indexes within their data. The next time the database conversion is triggered (when updating to a new version), the SAM Pro software will automatically install all active Custom Indexes (not flagged as Obsolete).


It is the responsibility of the user to configure the SQL correctly for their particular database. It is recommended that this viewer only be available to DBA/System level personnel.

Important Buttons:

image\createindex.gif Click this button to create this Custom Index within your database. Note that this record must be saved first.

image\dropindex.gif Click this button to drop this Custom Index.

Important Fields:

Custom Index Id:
This field must uniquely identify this record.

Index Name:
This field should have some relationship to its function. It SHOULD NOT include blanks as it will be referenced in the SQL Create String field. If its function is not obvious, consider using the Notes or Attachment features to add additional documentation.

Table Name:
Double-click on this field to select the table the index should be applied to.

SQL Create String:
This field must reference the exact Index Name noted in this record. The table referenced in the Create String must reference the internal database name, NOT the one selected in the Table Name field.

Sybase Example:

Custom Index Id: GLH01

Index Name: GLHistoryByDateEffective

Table Name: GLHistory

SQL Create String: Create Index GLHistoryByDateEffective on glhstry (glhstry_dte_effctve)

SQL Server Example:

Custom Index Id: GLH01

Index Name: GLHistoryByGLAccountRn

Table Name: GLHistory


on glhstry (glaccnt_rn)

INCLUDE (glentty_rn, glhstry_amnt_dbt, glhstry_amnt_crdt)