This shows you the differences between two versions of the page.
|
admin:indexing:activecounts:tips [2011/01/22 23:01] els |
admin:indexing:activecounts:tips [2016/06/28 22:38] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | {{page>:top_add&nofooter&noeditbtn}} | ||
| - | ====== Administration: Omnidex Indexing ====== | ||
| - | |||
| - | ===== ActiveCounts ===== | ||
| - | |||
| - | [[admin:indexing:activecounts:home|Overview]] | | ||
| - | [[admin:indexing:activecounts:example|Example]] | | ||
| - | [[admin:indexing:activecounts:sql|SQL]] | | ||
| - | [[admin:indexing:activecounts:optimization|Optimization]] | | ||
| - | **[[admin:indexing:activecounts:tips|Tips]]** | ||
| - | |||
| - | ---- | ||
| - | |||
| - | |||
| - | |||
| - | ==== Implementation Tips ==== | ||
| - | |||
| - | The following tips are helpful when implementing ActiveCounts in applications: | ||
| - | |||
| - | * ActiveCounts works best for lower-cardinality data since that produces a reasonable set of choices to display to the user. Criteria for high-cardinality data can be interwoven, but then it is best to just prompt for the criteria rather than display choices. Consider using the [[admin:indexing:autocomplete:home|AutoComplete]] feature for these criteria since it will show choices and can also show counts. | ||
| - | |||
| - | * The most important step in setting up ActiveCounts on a database is insuring that all statements are going to be completely optimized using Omnidex indexing. It is worthwhile to obtain a [[admin:optimization:plans:home|query plan]] for each query to insure that it is fully optimized. | ||
| - | |||
| - | * When ActiveCounts is used on an [[admin:features:grids:home|Omnidex Grid]], it can help performance to present the column used as the grid's [[admin:features:grids:partition|Partition Qualifier]] first. Once the Partition Qualifier has been provided, the scope of the searches is substantially reduced. | ||
| - | |||
| - | * When ActiveCounts is used on an [[admin:features:grids:home|Omnidex Grid]], it can help performance to have [[admin:features:rollups:home|Rollup Tables]] on each node, and also have Rollup Tables on a [[admin:features:grids:rollups|Rollup Node]]. | ||
| - | |||
| - | |||
| - | |||
| - | ===== ===== | ||
| - | |||
| - | **[[admin:indexing:activecounts:optimization|Prev]]** | ||
| - | |||
| - | |||
| - | ====== Additional Resources ====== | ||
| - | |||
| - | See also: | ||
| - | |||
| - | {{page>:admin:indexing:see_also&nofooter&noeditbtn}} | ||
| - | |||
| - | {{page>:bottom_add&nofooter&noeditbtn}} | ||