This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
glossary:a [2009/07/23 02:05] admin created |
glossary:a [2012/10/26 14:24] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | {{page>:top_add&nofooter&noeditbtn}} | ||
| + | <html><div align="center"><span style="color:red">DRAFT</span></div></html> | ||
| + | ====== Glossary ====== | ||
| ===== A ===== | ===== A ===== | ||
| + | {{page>:glossary_bar&nofooter&noeditbtn}} | ||
| + | ==== Access method ==== | ||
| + | * The process of operating in a database to store or retrieve data | ||
| + | * The movement of physical data to and from a computer and its storage devices | ||
| - | **access method** - The process of operating in a database to store or retrieve data | + | ==== Account Support Engineer ==== |
| - | The movement of physical data to and from a computer and its storage devices | + | * The DISC representative, also known as an ASE, involved in pre-sales customer support, providing early Omnidex design, administration and integration consulting services. |
| - | **Account Support Engineer** | + | ==== Active cursor ==== |
| - | The DISC representative, also known as an ASE, involved in pre-sales customer support, providing early database consulting services. | + | * The current internal Omnidex Access work space. See also: CURSOR. |
| - | **active cursor** | + | ==== Address ==== |
| - | The current internal Omnidex Access work space. See also: CURSOR. | + | * A numerical identifier for distinguishing one network node from another. |
| - | **address** | + | ==== Aggregation index ==== |
| - | A numerical identifier for distinguishing one network node from another. | + | * Keys to data based on the SQL functions COUNT, SUM, MIN, and MAX. See also: Aggregation/Sorted Key Index. |
| - | **aggregation index** | + | ==== Aggregation table ==== |
| - | Keys to data based on the SQL functions COUNT, SUM, MIN, and MAX. See also: Aggregation/Sorted Key Index. | + | * See Summary Table |
| + | ==== Aggregation/Sorted Key Index (ASK) ==== | ||
| + | * A type of Omnidex index that facilitates extremely high speed aggregations used primarily in OLAP and data warehousing applications. Aggregation/Sorted Key Indexes are commonly referred to as ASK Indexes. | ||
| + | * ASK Indexes generally combine multiple criteria fields along with one or more metric fields into a single composite index. ASK Indexes can also be used to provide sorted and linkage access to data files such as flat files that do not provide native sorted indexes. | ||
| + | ==== Aggregations ==== | ||
| + | * Summarizations of data, e.g., AVG, MIN, MAX, SUM, COUNT | ||
| + | * The process of summarzation (sum), averaging (AVG), finding the minimum (MIN) or maximum (MAX) values. | ||
| - | **aggregation table** See Summary Table | + | ==== AND criteria ==== |
| + | * Multiple criteria values or predicates that rows must match all or will not qualify. | ||
| - | **Aggregation/Sorted Key Index (ASK)** | + | ==== API ==== |
| - | A type of Omnidex index that facilitates extremely high speed aggregations used primarily in OLAP and data warehousing applications. Aggregation/Sorted Key Indexes are commonly referred to as ASK Indexes. | + | * Application Programming Interface: A collection of callable routines providing specific functions. Omnidex provides two different APIs. |
| - | ASK Indexes generally combine multiple criteria fields along with one or more metric fields into a single composite index. ASK Indexes can also be used to provide sorted and linkage access to data files such as flat files that do not provide native sorted indexes. | + | |
| - | **aggregations** | + | Omnidex supports four different API Interfaces: |
| - | Summarizations of data, e.g., AVG, MIN, MAX, SUM, COUNT | + | * ODBC - Open Data Base Connectivity |
| - | The process of summarzation (sum), averaging (AVG), finding the minimum (MIN) or maximum (MAX) values. | + | * JDBC - Jave Data Base Connectivity |
| + | * OA - OmniAccess | ||
| + | * CLOA - Client Omnidex Access | ||
| - | **AND criteria** | + | ==== ASK ==== |
| - | Multiple criteria values or predicates that rows must match all or will not qualify. | + | * Aggregation Sorted Keywork Index. |
| - | **API** | + | ==== ASK Index ==== |
| - | Application Programming Interface - a collection of callable routines providing specific functions. Omnidex provides two different APIs. | + | * See Aggregation/Sorted Key Index |
| - | SQL Language Interface with Omnidex extensions, which is callable through ODBC, JDBC and OmniAccess applications (via oaexecsql). | + | |
| - | Omnidex Access API, commonly referred to as the OA API. | + | |
| - | **ASK Index** | + | ==== ASK Order By Optimization ==== |
| - | See Aggregation/Sorted Key Index | + | |
| - | **asynchronous process** | + | ==== ASE ==== |
| - | A process whose execution proceeds independently of other processes, e.g. as a background process. | + | * Account Support Engineer. |
| - | **atomic data** | + | ==== Asynchronous process ==== |
| - | Information at the most simple level of detail, having low granularity. See also: granularity. | + | * A process whose execution proceeds independently of other processes, e.g. as a background process. |
| - | **AUTOPSEUDOCOLUMNS** | + | ==== Atomic data ==== |
| - | AUTOPSEUDOCOLUMNS causes Omnidex to automatically construct pseudocolumns from MDK composite keys. | + | * Information at the most simple level of detail, having low granularity. See also: granularity. |
| - | Aggregationa | + | ==== AUTOPSEUDOCOLUMNS ==== |
| - | ASK | + | * AUTOPSEUDOCOLUMNS causes Omnidex to automatically construct pseudocolumns from MDK composite keys. |
| - | ASK Indexes | + | |
| - | ASK Order By Optimization | + | |
| - | ====== Quick Links ====== | + | {{page>:bottom_add&nofooter&noeditbtn}} |
| - | {{page>:quicklinks&nofooter&noeditbtn}} | + | |