This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
glossary:h [2009/12/04 17:10] tdo |
glossary:h [2012/10/26 14:46] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | {{page>:top_add&nofooter&noeditbtn}} | ||
| + | <html><div align="center"><span style="color:red">DRAFT</span></div></html> | ||
| ====== Glossary ======= | ====== Glossary ======= | ||
| ===== H ===== | ===== H ===== | ||
| {{page>:glossary_bar&nofooter&noeditbtn}} | {{page>:glossary_bar&nofooter&noeditbtn}} | ||
| - | ===== hashed key ===== | + | ==== Hashed key ==== |
| + | * a database key facilitating direct access to data on a storage device. See key and direct access. | ||
| - | * a database key facilitating direct access to data on a storage device. See key and direct access. | + | ==== Hashing ==== |
| + | * An indexing technique where an algorithm is used to calculate the location of a row or record, requiring a full key look-up and an exact match, including upper and lower case characters, spaces, and punctuation. | ||
| - | ===== hashing ===== | + | ==== Having ==== |
| + | * An SQL statement clause that allows additional criteria to be applied to an SQL statement after the WHERE and GROUP BY clauses have been processed. The HAVING clause is generally used to apply criteria to an aggregation as in "SUM(ORDERS.TOTAL)>10". | ||
| - | * an indexing technique where an algorithm is used to calculate the location of a row or record, requiring a full key look-up and an exact match, including upper and lower case characters, spaces, and punctuation. | + | ==== HDC ==== |
| - | ===== having ===== | + | * Hashed Data Cache - This is an internal technique that Omnidex uses for internal optimization. It is an in memory hash table. |
| + | In OdxSQL Explain Plans, HDC can show up when reviewing optimization of a query. | ||
| - | * An SQL statement clause that allows additional criteria to be applied to an SQL statement after the WHERE and GROUP BY clauses have been processed. The HAVING clause is generally used to apply criteria to an aggregation as in "SUM(ORDERS.TOTAL)>10". | + | ==== High cardinality ==== |
| + | * (1) High table cardinality indicates a large number of records in a table, a Sales Fact table for example. | ||
| + | * (2) High column cadinality indicates many possible unique values in a column. For example, names, addresses, account balances, product inventories, etc. See cardinality. | ||
| - | ===== high cardinality ===== | ||
| - | * (1) High table cardinality indicates a large number of records in a table, a Sales Fact table for example. | + | ==== Hints ==== |
| - | * (2) High column cadinality indicates many possible unique values in a column. For example, names, addresses, account balances, product inventories, etc. See cardinality. | + | * A method of forcing the Omnidex Optimizer to use a particular retrieval method, in a star schema database environment, for example. |
| + | ==== Host ==== | ||
| + | * A generic term for any device that allows communication from an outside source. | ||
| - | ===== hints ===== | + | ==== Hybrid DR ==== |
| + | * Hybrid Detail Record; a variation of a multi-domain child, providing the ability to index a child table as a DR domain or in an SI domain. See DR domain and SI domain. | ||
| - | * a method of forcing the Omnidex Optimizer to use a particular retrieval method, in a star schema database environment, for example. | + | {{page>:bottom_add&nofooter&noeditbtn}} |
| - | ===== host ===== | ||
| - | |||
| - | * a generic term for any device that allows communication from an outside source. | ||
| - | |||
| - | |||
| - | ===== Hybrid DR ===== | ||
| - | |||
| - | |||
| - | * Hybrid Detail Record; a variation of a multi-domain child, providing the ability to index a child table as a DR domain or in an SI domain. See DR domain and SI domain. | ||
| - | |||
| - | |||
| - | ====== Quick Links ====== | ||
| - | {{page>:quicklinks&nofooter&noeditbtn}} | ||